E2EMatrixTrigger #13311
Triggered via workflow run
April 3, 2026 18:59
joshuakguo
completed
dec349e
Status
Failure
Total duration
21m 34s
Artifacts
–
e2e-matrix-trigger.yaml
on: workflow_run
resolve
/
resolve
7s
e2e-matrix
/
...
/
suite-upgrade
1m 46s
Matrix: e2e-matrix / e2e
Annotations
49 errors and 14 warnings
|
e2e-matrix / e2e-upgrade / suite-upgrade
The process '/usr/bin/git' failed with exit code 128
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
Process completed with exit code 254.
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
Process completed with exit code 254.
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
The process '/usr/bin/git' failed with exit code 128
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
unable to access 'https://github.com/aws/karpenter-provider-aws/': The requested URL returned error: 400
|
|
e2e-matrix / e2e (Termination, us-east-2, upstream) / suite-Termination
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Termination, us-east-2, upstream) / suite-Termination
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Termination, us-east-2, upstream) / suite-Termination
Process completed with exit code 255.
|
|
e2e-matrix / e2e (AMI, us-east-2, aws) / suite-AMI
Process completed with exit code 254.
|
|
e2e-matrix / e2e (AMI, us-east-2, aws) / suite-AMI
Process completed with exit code 254.
|
|
e2e-matrix / e2e (AMI, us-east-2, aws) / suite-AMI
Process completed with exit code 255.
|
|
e2e-matrix / e2e (LocalZone, us-west-2, aws) / suite-LocalZone
Process completed with exit code 254.
|
|
e2e-matrix / e2e (LocalZone, us-west-2, aws) / suite-LocalZone
Process completed with exit code 254.
|
|
e2e-matrix / e2e (LocalZone, us-west-2, aws) / suite-LocalZone
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Expiration, us-east-2, upstream) / suite-Expiration
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Expiration, us-east-2, upstream) / suite-Expiration
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Expiration, us-east-2, upstream) / suite-Expiration
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Storage, us-east-2, aws) / suite-Storage
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Storage, us-east-2, aws) / suite-Storage
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Storage, us-east-2, aws) / suite-Storage
Process completed with exit code 255.
|
|
e2e-matrix / e2e (NodeClaim, us-east-2, all) / suite-NodeClaim
Process completed with exit code 254.
|
|
e2e-matrix / e2e (NodeClaim, us-east-2, all) / suite-NodeClaim
Process completed with exit code 254.
|
|
e2e-matrix / e2e (NodeClaim, us-east-2, all) / suite-NodeClaim
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Chaos, us-east-2, upstream) / suite-Chaos
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Chaos, us-east-2, upstream) / suite-Chaos
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Chaos, us-east-2, upstream) / suite-Chaos
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Drift, us-east-2, all) / suite-Drift
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Drift, us-east-2, all) / suite-Drift
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Drift, us-east-2, all) / suite-Drift
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Interruption, us-east-2, aws) / suite-Interruption
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Interruption, us-east-2, aws) / suite-Interruption
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Interruption, us-east-2, aws) / suite-Interruption
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Integration, us-east-2, all) / suite-Integration
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Integration, us-east-2, all) / suite-Integration
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Integration, us-east-2, all) / suite-Integration
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Consolidation, us-east-2, aws) / suite-Consolidation
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Consolidation, us-east-2, aws) / suite-Consolidation
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Consolidation, us-east-2, aws) / suite-Consolidation
Process completed with exit code 255.
|
|
e2e-matrix / e2e (IPv6, us-east-2, aws) / suite-IPv6
Process completed with exit code 254.
|
|
e2e-matrix / e2e (IPv6, us-east-2, aws) / suite-IPv6
Process completed with exit code 254.
|
|
e2e-matrix / e2e (IPv6, us-east-2, aws) / suite-IPv6
Process completed with exit code 255.
|
|
e2e-matrix / e2e (Scheduling, us-east-2, aws) / suite-Scheduling
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Scheduling, us-east-2, aws) / suite-Scheduling
Process completed with exit code 254.
|
|
e2e-matrix / e2e (Scheduling, us-east-2, aws) / suite-Scheduling
Process completed with exit code 255.
|
|
e2e-matrix / e2e-upgrade / suite-upgrade
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@00943011d9042930efac3dcd3a170e4273319bc8, aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Termination, us-east-2, upstream) / suite-Termination
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (AMI, us-east-2, aws) / suite-AMI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (LocalZone, us-west-2, aws) / suite-LocalZone
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Expiration, us-east-2, upstream) / suite-Expiration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Storage, us-east-2, aws) / suite-Storage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (NodeClaim, us-east-2, all) / suite-NodeClaim
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Chaos, us-east-2, upstream) / suite-Chaos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Drift, us-east-2, all) / suite-Drift
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Interruption, us-east-2, aws) / suite-Interruption
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Integration, us-east-2, all) / suite-Integration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Consolidation, us-east-2, aws) / suite-Consolidation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (IPv6, us-east-2, aws) / suite-IPv6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|
|
e2e-matrix / e2e (Scheduling, us-east-2, aws) / suite-Scheduling
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708. 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/
|