fix(agents): pull-wake runner resilience — fetch cache stacking, hung… #73
KyleAMathewsagents_mobile_canary.yml
on: push
Detect mobile impact
20s
build
/
Build android canary
2m 20s
submit-play-internal
/
Build android canary-store
2m 21s
Annotations
7 errors and 3 warnings
|
build / Build android canary
Canceling since a higher priority waiting request for Agents Mobile Canary-refs/heads/main exists
|
|
build / Build android canary
The operation was canceled.
|
|
submit-play-internal / Build android canary-store
Canceling since a higher priority waiting request for Agents Mobile Canary-refs/heads/main exists
|
|
submit-play-internal / Build android canary-store
The operation was canceled.
|
|
Agents Mobile Canary
Canceling since a higher priority waiting request for Agents Mobile Canary-refs/heads/main exists
|
|
Agents Mobile Canary
Canceling since a higher priority waiting request for Agents Mobile Canary-refs/heads/main exists
|
|
Agents Mobile Canary
Canceling since a higher priority waiting request for Agents Mobile Canary-refs/heads/main exists
|
|
Detect mobile impact
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build / Build android canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
submit-play-internal / Build android canary-store
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|