Skip to content
ci

feat: add readiness risks handling and network policy management #140

Sign in to view logs

feat: add readiness risks handling and network policy management

feat: add readiness risks handling and network policy management #140

Triggered via push March 27, 2026 14:24
@lhy0718lhy0718
pushed ed30a92
main
Status Failure
Total duration 1m 48s
Artifacts –

ci.yml

on: push
build-and-test
1m 42s
build-and-test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
build-and-test
Process completed with exit code 1.
tests/doctorHarnessIntegration.test.ts > runDoctorReport > surfaces required networked execution as a stronger warning with explicit highlight guidance: tests/doctorHarnessIntegration.test.ts#L197
AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ tests/doctorHarnessIntegration.test.ts:197:38
tests/doctorHarnessIntegration.test.ts > runDoctorReport > downgrades declared networked execution to a warning instead of a hard failure: tests/doctorHarnessIntegration.test.ts#L160
AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ tests/doctorHarnessIntegration.test.ts:160:38
tests/doctorHarnessIntegration.test.ts > runDoctorReport > treats local snapshot isolation plus disabled network as ready for code execution: tests/doctorHarnessIntegration.test.ts#L123
AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ tests/doctorHarnessIntegration.test.ts:123:38
tests/doctorHarnessIntegration.test.ts > runDoctorReport > includes harness diagnostics for current workspace runs: tests/doctorHarnessIntegration.test.ts#L40
AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ tests/doctorHarnessIntegration.test.ts:40:38
build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/