Adapt to dyanmic side metadata address (jdk-21) #235
qinsoontest-pr.yml
on: pull_request
build-normal-fastdebug
/
linux-x64
1m 17s
build-vo-bit
/
linux-x64
1m 17s
build-extreme-assertions
/
linux-x64
1m 17s
build-malloc-mark-sweep
/
linux-x64
1m 16s
build-mark-in-header
/
linux-x64
1m 17s
build-forwarding-on-side
/
linux-x64
1m 16s
build-normal-release
/
linux-x64
1m 16s
Matrix: run-dacapo-2006 / Test feature build
Waiting for pending jobs
Matrix: run-dacapo-2006 / Test normal build
Waiting for pending jobs
Matrix: run-dacapo-chopin / normal-heap / test-normal-build
Waiting for pending jobs
Annotations
22 errors and 7 warnings
|
build-malloc-mark-sweep / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-malloc-mark-sweep / linux-x64
The operation was canceled.
|
|
build-normal-fastdebug / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-normal-fastdebug / linux-x64
The operation was canceled.
|
|
build-forwarding-on-side / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-forwarding-on-side / linux-x64
The operation was canceled.
|
|
build-normal-release / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-normal-release / linux-x64
The operation was canceled.
|
|
build-vo-bit / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-vo-bit / linux-x64
The operation was canceled.
|
|
build-extreme-assertions / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-extreme-assertions / linux-x64
The operation was canceled.
|
|
build-mark-in-header / linux-x64
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-mark-in-header / linux-x64
The operation was canceled.
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
DaCapo Tests
Canceling since a higher priority waiting request for DaCapo Tests-dynamic-side-metadata-address exists
|
|
build-malloc-mark-sweep / linux-x64
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/
|
|
build-normal-fastdebug / linux-x64
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/
|
|
build-forwarding-on-side / linux-x64
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/
|
|
build-normal-release / linux-x64
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/
|
|
build-vo-bit / linux-x64
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/
|
|
build-extreme-assertions / linux-x64
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/
|
|
build-mark-in-header / linux-x64
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/
|