bstein/bstein-dev-home
1
0
Fork 0
Code Issues 800 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[hermes] bstein-dev-home #567: playwright_page_setup_timeout #563

New Issue
Open
opened 2026-09-29 22:06:09 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-29 22:06:09 +00:00
Copy Link

Hermes auto-triage classified incident bstein-dev-home/567 as playwright_page_setup_timeout (confidence 0.75); first failed gate: tests.

Why a human is needed

Build 567 failed because both frontend browser component tests (metric-row.spec.js and stats-grid.spec.js) timed out after 30 seconds while Playwright was creating a browser page, on the first attempt and again on retry. The timeouts happened during test setup, before any component code ran, so the likely problem is the browser environment in CI — a missing or broken browser install, missing system dependencies, or a starved build pod — not the components under test. The build went red in the 'Publish test metrics' stage, which evaluates the test results, and the backend build/push was skipped. Deciding between an environment problem and a repository change (for example a Playwright or config bump) needs evidence not present here: the archived error-context files under test-results/, a traced re-run, and the agent pod's resource state; centralized logs for the window were also unreachable. Separately and non-fatally, Node.js is absent from the SonarQube scanner environment, so JavaScript/TypeScript analysis is silently skipped; adding Node.js to that image would restore it.

Ariadne did not authorize automated remediation: human_required.

Facts

  • jenkins — Build bstein-dev-home #567 ran from 2026-09-29T21:26:00Z to 2026-09-29T22:02:34Z and finished FAILURE. (https://ci.bstein.dev/job/bstein-dev-home/567/ (jenkins.result, jenkins.timestamps))
  • jenkins — jenkins.first_failed_stage is 'Publish test metrics'; the pipeline ended with 'ERROR: script returned exit code 1' and 'Build & push backend' was skipped due to earlier failure(s). (jenkins.first_failed_stage; jenkins.console_tail)
  • jenkins — Two frontend browser component tests failed, each on the first attempt and on Retry #1, all with 'Test timeout of 30000ms exceeded while setting up "page"' from browserContext.newPage: testing/frontend/component/metric-row.spec.js:5:5 'renders metric values in the browser' and testing/frontend/co... (jenkins.console_failures line 839)
  • jenkins — jenkins.failed_tests is empty; the build published no structured test results, so the console excerpt is the only test-level evidence. (jenkins.failed_tests)
  • jenkins — After the two test failures the frontend 'prebuild' and 'build' npm scripts still started, so the test run did not immediately abort the shell step. (jenkins.console_failures line 839 (trailing lines))
  • jenkins — At 21:32:50 the SonarQube scanner logged NodeCommandException / 'Cannot run program "node": error=2, No such file or directory' in the JavaScript sensor; the sensor then completed ('Sensor JavaScript analysis [javascript] (done)') and the scan continued into the TypeScript sensor, and the failed ... (jenkins.console_failures lines 348 and 384)
  • opensearch — Correlated log evidence is unavailable for this incident window: the OpenSearch query returned zero records with error 'opensearch request failed: [Errno 111] Connection refused'. (log_evidence.error, query window 2026-09-29T21:21:00Z to 22:07:34Z)

Evidence

The earliest failure region of the build console:

21:32:34.534 INFO  Sensor JaCoCo XML Report Importer [jacoco] (done) | time=10ms
21:32:34.535 INFO  Sensor IaC CloudFormation Sensor [iac]
21:32:35.322 INFO  0 source files to be analyzed
21:32:35.518 INFO  0/0 source files have been analyzed
21:32:35.519 INFO  Sensor IaC CloudFormation Sensor [iac] (done) | time=984ms
21:32:35.520 INFO  Sensor IaC Kubernetes Sensor [iac]
21:32:35.728 INFO  0 source files to be analyzed
21:32:35.917 INFO  0/0 source files have been analyzed
21:32:35.918 INFO  Sensor IaC Kubernetes Sensor [iac] (done) | time=399ms
21:32:35.918 INFO  Sensor JavaScript analysis [javascript]
21:32:50.368 ERROR Error when running: 'node -v'. Is Node.js available during analysis?
org.sonarsource.nodejs.NodeCommandException: Error when running: 'node -v'. Is Node.js available during analysis?
	at org.sonarsource.nodejs.NodeCommand.start(NodeCommand.java:79)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.getVersion(NodeCommandBuilderImpl.java:203)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.checkNodeCompatibility(NodeCommandBuilderImpl.java:169)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.build(NodeCommandBuilderImpl.java:143)
	at org.sonar.plugins.javascrip
... (truncated; the full log is in the linked build)

Inferences

  • The first enforced failure is the frontend browser component test run: both failing tests died identically in Playwright's page fixture setup (browserContext.newPage timed out at 30s) before any test body executed, and both retries reproduced it. That pattern points to the browser not being able ...
  • The build most plausibly turned red when the 'Publish test metrics' stage aggregated the test results and exited 1 on the two failures; the console shows no error from the publishing machinery itself in the retained excerpts, so the stage appears to be reporting the test failures rather than fail...
  • The Sonar Node.js error is a separate latent problem, not the cause of this failure: the scan continued past it and the build failed elsewhere. It does mean JavaScript/TypeScript files are currently not analyzed at all; installing Node.js in the scanner environment would restore that analysis.
  • A fix would involve reproducing the Playwright run in the same CI image with traces enabled (npx playwright test --trace on), verifying that the pinned Playwright version's browsers are installed with their system dependencies (npx playwright install --with-deps), reading the archived error-conte...

Suggested remediation (not available)

No automated remediation exists for this failure. Hermes proposes one; it was not performed, and Ariadne cannot perform it until a person builds and deploys it.

  • Proposed action: rerun_browser_tests_on_fresh_agent
  • What it would do: Re-run the failed frontend browser test stage once on a freshly provisioned agent pod with Playwright tracing enabled and the test-results/ error-context artifacts archived, to separate an agent-local browser-launch problem from a repository regression.
  • Evidence that should be required first: Every failed browser test failed during Playwright fixture setup (browser launch or browserContext.newPage timeout) on all attempts including retries, with zero in-test assertion failures in the structured results or console output.

Links

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

Hermes auto-triage classified incident `bstein-dev-home/567` as **playwright_page_setup_timeout** (confidence 0.75); first failed gate: `tests`. ## Why a human is needed Build 567 failed because both frontend browser component tests (metric-row.spec.js and stats-grid.spec.js) timed out after 30 seconds while Playwright was creating a browser page, on the first attempt and again on retry. The timeouts happened during test setup, before any component code ran, so the likely problem is the browser environment in CI — a missing or broken browser install, missing system dependencies, or a starved build pod — not the components under test. The build went red in the 'Publish test metrics' stage, which evaluates the test results, and the backend build/push was skipped. Deciding between an environment problem and a repository change (for example a Playwright or config bump) needs evidence not present here: the archived error-context files under test-results/, a traced re-run, and the agent pod's resource state; centralized logs for the window were also unreachable. Separately and non-fatally, Node.js is absent from the SonarQube scanner environment, so JavaScript/TypeScript analysis is silently skipped; adding Node.js to that image would restore it. Ariadne did not authorize automated remediation: `human_required`. ## Facts - **jenkins** — Build bstein-dev-home #567 ran from 2026-09-29T21:26:00Z to 2026-09-29T22:02:34Z and finished FAILURE. (`https://ci.bstein.dev/job/bstein-dev-home/567/ (jenkins.result, jenkins.timestamps)`) - **jenkins** — jenkins.first_failed_stage is 'Publish test metrics'; the pipeline ended with 'ERROR: script returned exit code 1' and 'Build & push backend' was skipped due to earlier failure(s). (`jenkins.first_failed_stage; jenkins.console_tail`) - **jenkins** — Two frontend browser component tests failed, each on the first attempt and on Retry #1, all with 'Test timeout of 30000ms exceeded while setting up "page"' from browserContext.newPage: testing/frontend/component/metric-row.spec.js:5:5 'renders metric values in the browser' and testing/frontend/co... (`jenkins.console_failures line 839`) - **jenkins** — jenkins.failed_tests is empty; the build published no structured test results, so the console excerpt is the only test-level evidence. (`jenkins.failed_tests`) - **jenkins** — After the two test failures the frontend 'prebuild' and 'build' npm scripts still started, so the test run did not immediately abort the shell step. (`jenkins.console_failures line 839 (trailing lines)`) - **jenkins** — At 21:32:50 the SonarQube scanner logged NodeCommandException / 'Cannot run program "node": error=2, No such file or directory' in the JavaScript sensor; the sensor then completed ('Sensor JavaScript analysis [javascript] (done)') and the scan continued into the TypeScript sensor, and the failed ... (`jenkins.console_failures lines 348 and 384`) - **opensearch** — Correlated log evidence is unavailable for this incident window: the OpenSearch query returned zero records with error 'opensearch request failed: [Errno 111] Connection refused'. (`log_evidence.error, query window 2026-09-29T21:21:00Z to 22:07:34Z`) ## Evidence The earliest failure region of the build console: ``` 21:32:34.534 INFO Sensor JaCoCo XML Report Importer [jacoco] (done) | time=10ms 21:32:34.535 INFO Sensor IaC CloudFormation Sensor [iac] 21:32:35.322 INFO 0 source files to be analyzed 21:32:35.518 INFO 0/0 source files have been analyzed 21:32:35.519 INFO Sensor IaC CloudFormation Sensor [iac] (done) | time=984ms 21:32:35.520 INFO Sensor IaC Kubernetes Sensor [iac] 21:32:35.728 INFO 0 source files to be analyzed 21:32:35.917 INFO 0/0 source files have been analyzed 21:32:35.918 INFO Sensor IaC Kubernetes Sensor [iac] (done) | time=399ms 21:32:35.918 INFO Sensor JavaScript analysis [javascript] 21:32:50.368 ERROR Error when running: 'node -v'. Is Node.js available during analysis? org.sonarsource.nodejs.NodeCommandException: Error when running: 'node -v'. Is Node.js available during analysis? at org.sonarsource.nodejs.NodeCommand.start(NodeCommand.java:79) at org.sonarsource.nodejs.NodeCommandBuilderImpl.getVersion(NodeCommandBuilderImpl.java:203) at org.sonarsource.nodejs.NodeCommandBuilderImpl.checkNodeCompatibility(NodeCommandBuilderImpl.java:169) at org.sonarsource.nodejs.NodeCommandBuilderImpl.build(NodeCommandBuilderImpl.java:143) at org.sonar.plugins.javascrip ... (truncated; the full log is in the linked build) ``` ## Inferences - The first enforced failure is the frontend browser component test run: both failing tests died identically in Playwright's page fixture setup (browserContext.newPage timed out at 30s) before any test body executed, and both retries reproduced it. That pattern points to the browser not being able ... - The build most plausibly turned red when the 'Publish test metrics' stage aggregated the test results and exited 1 on the two failures; the console shows no error from the publishing machinery itself in the retained excerpts, so the stage appears to be reporting the test failures rather than fail... - The Sonar Node.js error is a separate latent problem, not the cause of this failure: the scan continued past it and the build failed elsewhere. It does mean JavaScript/TypeScript files are currently not analyzed at all; installing Node.js in the scanner environment would restore that analysis. - A fix would involve reproducing the Playwright run in the same CI image with traces enabled (npx playwright test --trace on), verifying that the pinned Playwright version's browsers are installed with their system dependencies (npx playwright install --with-deps), reading the archived error-conte... ## Suggested remediation (not available) No automated remediation exists for this failure. Hermes proposes one; it was not performed, and Ariadne cannot perform it until a person builds and deploys it. - Proposed action: `rerun_browser_tests_on_fresh_agent` - What it would do: Re-run the failed frontend browser test stage once on a freshly provisioned agent pod with Playwright tracing enabled and the test-results/ error-context artifacts archived, to separate an agent-local browser-launch problem from a repository regression. - Evidence that should be required first: Every failed browser test failed during Playwright fixture setup (browser launch or browserContext.newPage timeout) on all attempts including retries, with zero in-test assertion failures in the structured results or console output. ## Links - Failed build: https://ci.bstein.dev/job/bstein-dev-home/567/ - 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_cd6a8cc3f814402087471fee7288c21c](https://triage.bstein.dev/chat?resume=run_cd6a8cc3f814402087471fee7288c21c)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=bstein-dev-home classification=playwright_page_setup_timeout incident=bstein-dev-home/567 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bstein
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bstein/bstein-dev-home#563
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?