[hermes] bstein-dev-home #448: frontend_e2e_test_timeout #14

New Issue

bstein · 2026-08-06T21:44:33Z

bstein commented

2026-08-06 21:44:33 +00:00

Hermes auto-triage classified incident bstein-dev-home/448 as frontend_e2e_test_timeout (confidence 0.95); first failed gate: Enforce quality gate.

Why a human is needed

The build is blocked by a frontend Playwright end-to-end test that waited 60 seconds for the Escape key interaction used to close the platform-diagram overlay. The backend suite is healthy, so the fix should focus on the homepage overlay dismissal behavior and the test's waiting conditions: reproduce the interaction, confirm that Escape reliably closes the visible overlay, and correct either the event-handling/rendering path or any invalid test synchronization. Separately, the CI image used for Sonar analysis lacks Node.js; restore Node.js to that analysis environment so JavaScript analysis can run correctly, but do not treat that earlier scanner error as the proven build-stopping failure from this bundle.

Ariadne did not authorize automated remediation: classification_not_supported: 'frontend_e2e_test_timeout'.

Facts

jenkins — Jenkins build 448 for bstein-dev-home ended with result FAILURE after 1028.09 seconds. (https://ci.bstein.dev/job/bstein-dev-home/448/)
jenkins — Jenkins reported the first failed pipeline stage as "Enforce quality gate". (build 448 jenkins.first_failed_stage)
jenkins — The backend test command completed successfully: 128 tests passed in 38.38 seconds and wrote JUnit and coverage XML artifacts. (build 448 console failure excerpt at line 693)
jenkins — The frontend Playwright test "shows Brad's professional homepage and opens the platform diagram overlay" timed out after 60000 ms while executing page.keyboard.press("Escape") at testing/frontend/e2e/home.spec.js:102. (build 448 console failure excerpt at line 901)
jenkins — The structured jenkins.failed_tests field is empty, so the failing frontend test evidence comes from the chronological console failure excerpt. (build 448 jenkins.failed_tests)
jenkins — Earlier in the build, Sonar JavaScript analysis reported that the node executable was unavailable, with "Cannot run program "node": error=2, No such file or directory". (build 448 console failure excerpts at lines 339 and 375)

Inferences

The enforced build failure is attributable to the frontend end-to-end test timeout, because the backend suite passed and the reported failed stage is the later quality-gate enforcement stage.
The overlay was visible before Escape was pressed, but the browser action did not complete within the test timeout. The frontend overlay dismissal path, page responsiveness, or the test's synchronization around that interaction needs investigation.
The missing Node.js executable during Sonar JavaScript analysis is an earlier CI-image configuration defect or degraded analysis condition, but the supplied evidence does not establish that it was the enforced failure for this build; the pipeline continued to backend and frontend testing afterward.

Links

Failed build: https://ci.bstein.dev/job/bstein-dev-home/448/
Full evidence bundle and audit trail live in Ariadne at /api/admin/audit/events, event types hermes_autotriage_incident and hermes_autotriage_diagnosis.

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_c56538035d554d93b188fcb8a4254b51). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `bstein-dev-home/448` as **frontend_e2e_test_timeout** (confidence 0.95); first failed gate: `Enforce quality gate`. ## Why a human is needed The build is blocked by a frontend Playwright end-to-end test that waited 60 seconds for the Escape key interaction used to close the platform-diagram overlay. The backend suite is healthy, so the fix should focus on the homepage overlay dismissal behavior and the test's waiting conditions: reproduce the interaction, confirm that Escape reliably closes the visible overlay, and correct either the event-handling/rendering path or any invalid test synchronization. Separately, the CI image used for Sonar analysis lacks Node.js; restore Node.js to that analysis environment so JavaScript analysis can run correctly, but do not treat that earlier scanner error as the proven build-stopping failure from this bundle. Ariadne did not authorize automated remediation: `classification_not_supported: 'frontend_e2e_test_timeout'`. ## Facts - **jenkins** — Jenkins build 448 for bstein-dev-home ended with result FAILURE after 1028.09 seconds. (`https://ci.bstein.dev/job/bstein-dev-home/448/`) - **jenkins** — Jenkins reported the first failed pipeline stage as "Enforce quality gate". (`build 448 jenkins.first_failed_stage`) - **jenkins** — The backend test command completed successfully: 128 tests passed in 38.38 seconds and wrote JUnit and coverage XML artifacts. (`build 448 console failure excerpt at line 693`) - **jenkins** — The frontend Playwright test "shows Brad's professional homepage and opens the platform diagram overlay" timed out after 60000 ms while executing page.keyboard.press("Escape") at testing/frontend/e2e/home.spec.js:102. (`build 448 console failure excerpt at line 901`) - **jenkins** — The structured jenkins.failed_tests field is empty, so the failing frontend test evidence comes from the chronological console failure excerpt. (`build 448 jenkins.failed_tests`) - **jenkins** — Earlier in the build, Sonar JavaScript analysis reported that the node executable was unavailable, with "Cannot run program \"node\": error=2, No such file or directory". (`build 448 console failure excerpts at lines 339 and 375`) ## Inferences - The enforced build failure is attributable to the frontend end-to-end test timeout, because the backend suite passed and the reported failed stage is the later quality-gate enforcement stage. - The overlay was visible before Escape was pressed, but the browser action did not complete within the test timeout. The frontend overlay dismissal path, page responsiveness, or the test's synchronization around that interaction needs investigation. - The missing Node.js executable during Sonar JavaScript analysis is an earlier CI-image configuration defect or degraded analysis condition, but the supplied evidence does not establish that it was the enforced failure for this build; the pipeline continued to backend and frontend testing afterward. ## Links - Failed build: https://ci.bstein.dev/job/bstein-dev-home/448/ - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run `run_c56538035d554d93b188fcb8a4254b51`). Hermes has no write access to this repository; no files or infrastructure were changed.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bstein/bstein-dev-home#14