Skip to content

docs harness: 'verify-docs reports pass/fail counts' stalls on CI #4450

Closed

Description

@bpamiri

The docs-harness test "verify-docs reports pass/fail counts" (web/sites/guides/scripts/verify-docs/test/orchestrator.test.mjs) stalls on CI.

The test doesn't print the child's output, so the log doesn't say which wheels command stalls. In the child, it's either the warm-up wheels system paths, the {test:cli} / {test:compile} blocks, or the tutorial step's wheels new.

Since #4444, the harness step is blocking, so this fails "Verify docs" on PRs.

Next:

  1. The test prints the child's stdout/stderr when it fails, so CI names the stuck command.
  2. On CI it's skipped (not failed) while this is open.
  3. Find and fix the stall, then remove the skip.

Activity

  1. added this to the v4.2.0 milestone on Oct 6, 2026
  2. self-assigned this
    on Oct 6, 2026
  3. bpamiri commented on Oct 6, 2026

    @bpamiri
    CollaboratorAuthor

    Root cause and fix (PR #4452):

    • Cause: wheels JVMs starting at the same moment in one CLI home race in Lucee's OSGi bundle cache: BundleException: Bundle symbolic name and version are not unique, then a null script engine. Lucee's loader runs with felix.cache.locking=false and installs its required bundles on every start, so simultaneous starts collide.
    • Not fixed by: -Dfelix.cache.locking=true (3 of 12 runs still failed), or copying an already-warm lucee-server/ into the home (3 of 8 failed).
    • Fixed by: staggering starts by ≥ 250 ms (0 of 12 failed; 6 of 12 with no gap). fix(docs): stagger wheels JVM starts so concurrent blocks don't race in Lucee's bundle cache #4452 staggers wheels starts in the docs harness by 1 s and re-enables the test without a skip.
    • Beyond the harness: this isn't specific to the harness. Users running several wheels commands at once against one CLI home can hit it too. An upstream report for the Lucee/LuCLI side is drafted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions