Skip to content

Planner executor agent improvements with plan verification, etc #593

Planner executor agent improvements with plan verification, etc

Planner executor agent improvements with plan verification, etc #593

Triggered via pull request March 15, 2026 06:11
Status Failure
Total duration 8m 28s
Artifacts

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 3 warnings
test (ubuntu-latest, 3.11)
Process completed with exit code 1.
test (ubuntu-latest, 3.11)
Process completed with exit code 1.
test (ubuntu-latest, 3.11)
Process completed with exit code 127.
test (ubuntu-latest, 3.11)
Process completed with exit code 1.
test (ubuntu-latest, 3.11)
Process completed with exit code 1.
test (macos-latest, 3.11)
The strategy configuration was canceled because "test.ubuntu-latest_3_11" failed
test (macos-latest, 3.11)
The operation was canceled.
test (macos-latest, 3.11)
Process completed with exit code 1.
test (macos-latest, 3.11)
Process completed with exit code 127.
test (macos-latest, 3.11)
Process completed with exit code 1.
test (macos-latest, 3.11)
Process completed with exit code 1.
test (windows-latest, 3.11)
The strategy configuration was canceled because "test.ubuntu-latest_3_11" failed
test (windows-latest, 3.11)
The operation was canceled.
test (windows-latest, 3.11)
Process completed with exit code 1.
test (windows-latest, 3.11)
Process completed with exit code 1.
test (windows-latest, 3.11)
Process completed with exit code 1.
test (windows-latest, 3.11)
Process completed with exit code 1.
test (ubuntu-latest, 3.11)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
test (macos-latest, 3.11)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
test (windows-latest, 3.11)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/