Skip to content

fix(ci): diagnose WebUI startup and reserve macOS artifact time - #54

Open
Fectivnfy112357 wants to merge 10 commits into
fix/confirmed-webui-release-issuesfrom
fix/webui-ci-startup-diagnostics
Open

Fectivnfy112357 wants to merge 10 commits into
fix/confirmed-webui-release-issuesfrom
fix/webui-ci-startup-diagnostics

Conversation

@Fectivnfy112357

@Fectivnfy112357 Fectivnfy112357 commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Change

The Windows main job in run 44650750776 failed because the isolated development server did not report readiness within 20 seconds. The test discarded stderr. Preserve opt-in startup phase timings on timeout or early exit, without retaining raw child output or the launcher credential. Disable managed-provider setup for the isolated shutdown fixture and give its cold startup up to 40 seconds. Shutdown still has its own 20-second deadline.

In the same run macOS passed units before the windowed browser suite exhausted the 40-minute job cap. Set a 60-minute macOS job budget and a separate 30-minute browser-step limit, leaving time to upload evidence. Per-test assertions, retry count and coverage are unchanged.

This PR is stacked on #50 for committed source inventory assets. Retarget it to main after #50 lands.

Validation

  • The real isolated development entry started, rejected unauthenticated shutdown, acknowledged authenticated shutdown and exited on Linux.
  • Release-tools contracts: 65 pass, 1 platform skip. Git diff check and AOCI alignment passed.
  • Hosted macOS and Windows validation is needed. The original Windows timeout root cause remains unknown and other browser assertion failures are under investigation.

Rail asset readiness

Windows run 44655509348 failed in the desktop-dark rail test's local-image wait. The old assertion printed only a boolean. Commit df7a15398 preserves the readiness predicate and reports the path, completion flag, natural width and loading mode of images that have not settled. Query strings stay out of logs. Three repeats of the three rail variants passed on Linux, and a controlled broken-image browser probe verified the failure evidence.

macOS account-menu hover

The macOS browser run 44655509348 failed with two expected usage-quota requests and three actual. The test's command round trips could let the application's 180 ms close timer expire between pointer moves. A controlled 250 ms runner delay produced the same 2/3 failure on Linux. Commit 32e1b6beb drives the grace timer with Playwright's browser clock, verifies that short gaps do not refresh, then advances past the close timeout and checks that an explicit reopen does refresh. The same 250 ms runner delay passed after the change, and all 30 account-login browser cases passed across three repeats.

The downloaded macOS Playwright trace confirms the real runner timing: a settings-row mouse move began at 16000.523 ms and the corresponding return to the usage row began at 16435.173 ms, a 434.650 ms gap. The trace's request-count assertion recorded the same expected 2 / actual 3 failure.

The recovered Windows trace names the failed request: /assets/img/minimax-octopus-composer-poster.png failed with Chromium net::ERR_NO_BUFFER_SPACE. It was the only failed request in the trace; the other 14 responses were HTTP 200, including the neighboring rail images. No replacement WebP request appears. This confirms the failure was a browser network error rather than a missing fixture file or a measured layout assertion. The historical runner has no socket census, so it is not possible to attribute the resource error to ephemeral port exhaustion from that trace alone.

The Windows job on #53 (run 44660064752, job 136035992620) reproduced the same net::ERR_NO_BUFFER_SPACE on the initial loopback document request in the browser notice test. The document did not load and the notice assertion was never reached. The other 514 browser cases, the native terminal acceptance, unit/integration tests and package installation passed. Together the two failures establish that different loopback resources can be affected. The staged diagnostic captures aggregate Windows TCP states on this event; it will be pushed after the current #54 run to preserve the baseline comparison.

Update: the Windows mitigation in 69689ef29 backports Playwright #43605 for the pinned 1.63.0 test browser. Both observed Windows failures match the upstream error. The launch option replaces the exact default switch and leaves all 15 original disabled features intact. A real Chromium CDP probe verified one effective switch with the additional feature, and the four formerly implicated browser scenarios passed on Linux. The branch also includes the bounded TCP-state attachment from 3c9fdca10. Hosted Windows behavior remains to be validated. The new push supersedes the prior baseline run.

Windows FFmpeg provisioning

Windows jobs 136048303738 and 136050981740 received HTTP 503 and 504 respectively from Chocolatey and installed zero packages. Both jobs continued into the tests. Five unit/integration cases and five browser cases then failed with FFmpeg ENOENT.

The Windows setup now downloads the versioned Gyan 9.0.2 essentials ZIP linked from FFmpeg's downloads page, verifies its pinned SHA-256 before extraction and adds the bin directory to subsequent steps. Node must successfully launch FFmpeg before the unit and browser suites run. The workflow contract and AOCI entries are updated. The release-tools suite passed 65 tests with one platform skip.

With the Chromium workaround active, job 136050981740 passed 510 browser cases, including the native terminal acceptance. Its five browser failures were all FFmpeg ENOENT, and the completed raw log did not contain ERR_NO_BUFFER_SPACE. This is one clean Windows observation for that particular browser error. The new full matrix for both fixes is run 44668827277.

Hosted matrix follow-up

Run 44668827277 passed Ubuntu and macOS, including the headed macOS browser suite and diagnostics upload. Windows ran Gyan FFmpeg 9.0.2, passed all 515 browser cases and passed package installation. Its only failure was Browser Core inspection returning zero elements on the first fixture page after the scanner logged a generic CDP “Uncaught”. Commit b963f0e waits for the fixture document title before inspection and includes the current title on an empty result. This is a readiness mitigation while the exact CDP exception remains unknown. The five real-Chromium integration cases passed in five consecutive Linux runs.

In earlier macOS run 44663860357, the real Design browser test reported ENOENT during template deletion. A deterministic filesystem interleaving reproduced the error at readFile; the fix in 0695bd2 also covers deletion before lstat. The Linux real-browser workflow and 29 focused unit/integration cases passed. Both fixes and their AOCI updates are now on this PR.

The full WebUI CI matrix passed on Ubuntu, Windows and macOS at commit b963f0e14. Windows passed all 5 Browser Core Agent integration cases, 4,644 unit/integration cases overall (10 skipped), and all 515 Playwright cases. macOS passed the headed browser suite and package installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant