Run Claude and Codex ACP adapters in VM containers #904
shivammittal274test.yml
on: pull_request
Matrix: test
PR test summary
6s
Annotations
6 errors and 12 warnings
|
Tests / server-api
Process completed with exit code 1.
|
|
error: ENOENT: no such file or directory:
packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts#L563
at <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:563:20)
at async withHermesBrowserosDir (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:617:18)
at async <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:544:11)
|
|
error: ENOENT: no such file or directory:
packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts#L530
at <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:530:20)
at async withHermesBrowserosDir (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:617:18)
at async <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:512:11)
|
|
error: ENOENT: no such file or directory:
packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts#L466
at <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:466:20)
at async withHermesBrowserosDir (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:617:18)
at async <anonymous> (/home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/api/services/agents/agent-harness-service.test.ts:449:11)
|
|
Tests / server-tools
Process completed with exit code 1.
|
|
AssertionError: Expected page content:
packages/browseros-agent/apps/server/tests/tools/observation.test.ts#L166
at /home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/tools/observation.test.ts:166:14
at /home/runner/work/BrowserOS/BrowserOS/packages/browseros-agent/apps/server/tests/__helpers__/with-browser.ts:86:11
at processTicksAndRejections (native:7:39)
|
|
Tests / server-skills
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / eval
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-browser
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / agent
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-lib
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-root
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-agent
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Tests / server-integration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
|
|
Tests / server-tools
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@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/
|
|
PR test summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/github-script@v7. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
junit-agent
Expired
|
4.3 KB |
sha256:67ef8c451b507cbd0f9352cba33fa97eac056cc607bd22ed2b9bb9a05e45c083
|
|
|
junit-build
Expired
|
846 Bytes |
sha256:b586e9eeb2da938a7366abcff281d9326d78219957bece46981850019f2326ba
|
|
|
junit-eval
Expired
|
4.67 KB |
sha256:7a35108998c30e50fa18214f89be34550c16dd4d9a7db6637df3f071066e4f58
|
|
|
junit-server-agent
Expired
|
8.23 KB |
sha256:a8dd704da879018a0be7ec34461a30f17db2d8f981a7a48b61291a7cb4bb9784
|
|
|
junit-server-api
Expired
|
7.97 KB |
sha256:54e9d039b2e23129fcbad56b437665ae9695daf6ef30a4594ee9a11831e8e365
|
|
|
junit-server-browser
Expired
|
650 Bytes |
sha256:99ea0b1aa1e1bdfdc6b9e97b785cfe09e3ffd0a6b80a390c5ba62d1c7e0cf087
|
|
|
junit-server-integration
Expired
|
1.03 KB |
sha256:aeeb2e2113c425b2e37f9d04edf59223d393c5d4b4ef5c708b0f3d143b78d63f
|
|
|
junit-server-lib
Expired
|
10.4 KB |
sha256:2f9f40e1eb36a5dadbfa763ab801fe6dade1be7d27ada2b652b443e408f02a16
|
|
|
junit-server-root
Expired
|
2.91 KB |
sha256:05d8026bca1f87c76f17360e0394e0c8be86ecf173c4d86741a4d2bea0c2fd03
|
|
|
junit-server-skills
Expired
|
1.46 KB |
sha256:9e5b1d168ae93fe0a9c111bd0337676e7e961ca77670b65ba2b5c81301aa009f
|
|
|
junit-server-tools
Expired
|
6.84 KB |
sha256:275f540e77b39105db532e4225df682d9121c94718aaa33da08b41138300aea4
|
|