claim: ALIiAr5ZhQDz by beagle-ab2-44416 #373
Annotations
28 errors and 3 warnings
|
test (ubuntu-latest)
Process completed with exit code 1.
|
|
test (ubuntu-latest)
[-] jobs lists background processes 26ms (25ms|1ms)
|
|
test (ubuntu-latest)
[-] Invoke-BashSleep 0.1 & syntax sets background process 26ms (21ms|5ms)
|
|
test (ubuntu-latest)
[-] selects job by number 40ms (14ms|26ms)
|
|
test (ubuntu-latest)
[-] brings a running job to foreground and waits 11ms (10ms|1ms)
|
|
test (ubuntu-latest)
[-] waits for all background jobs 9ms (8ms|1ms)
|
|
test (ubuntu-latest)
[-] waits for a specific PID 8ms (7ms|1ms)
|
|
test (ubuntu-latest)
[-] Describe Invoke-BashJobs failed
|
|
test (ubuntu-latest)
[-] launches a background process 21ms (20ms|1ms)
|
|
test (windows-latest)
Process completed with exit code 1.
|
|
test (windows-latest)
[-] jobs lists background processes 19ms (15ms|4ms)
|
|
test (windows-latest)
[-] Invoke-BashSleep 0.1 & syntax sets background process 52ms (8ms|44ms)
|
|
test (windows-latest)
[-] selects job by number 5ms (4ms|0ms)
|
|
test (windows-latest)
[-] brings a running job to foreground and waits 380ms (9ms|371ms)
|
|
test (windows-latest)
[-] waits for all background jobs 6ms (6ms|1ms)
|
|
test (windows-latest)
[-] waits for a specific PID 7ms (5ms|2ms)
|
|
test (windows-latest)
[-] Describe Invoke-BashJobs failed
|
|
test (windows-latest)
[-] launches a background process 18ms (16ms|2ms)
|
|
test (macos-latest)
Process completed with exit code 1.
|
|
test (macos-latest)
[-] jobs lists background processes 159ms (158ms|1ms)
|
|
test (macos-latest)
[-] Invoke-BashSleep 0.1 & syntax sets background process 287ms (286ms|1ms)
|
|
test (macos-latest)
[-] selects job by number 93ms (85ms|9ms)
|
|
test (macos-latest)
[-] brings a running job to foreground and waits 91ms (86ms|4ms)
|
|
test (macos-latest)
[-] waits for all background jobs 77ms (77ms|1ms)
|
|
test (macos-latest)
[-] waits for a specific PID 68ms (63ms|5ms)
|
|
test (macos-latest)
[-] Describe Invoke-BashJobs failed
|
|
test (macos-latest)
[-] launches a background process 61ms (61ms|1ms)
|
|
test (macos-latest)
[-] ps -A is equivalent to -e 659ms (653ms|6ms)
|
|
test (ubuntu-latest)
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 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/
|
|
test (windows-latest)
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 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/
|
|
test (macos-latest)
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 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/
|