[DRAFT] Add Adam Support for Generic and Siracusa Platforms #95
runwangdlci-platform-gap9-tiled.yml
on: pull_request
select-env
/
select
3s
gap9-kernels-tiled-singlebuffer-L2
/
test-runner-gap9-tiled
24m 35s
gap9-kernels-tiled-doublebuffer-L2
/
test-runner-gap9-tiled
23m 30s
gap9-models-tiled-singlebuffer-L2
/
test-runner-gap9-tiled
15m 12s
gap9-models-tiled-doublebuffer-L2
/
test-runner-gap9-tiled
21m 38s
Annotations
4 errors and 4 warnings
|
gap9-models-tiled-singlebuffer-L2 / test-runner-gap9-tiled
Process completed with exit code 1.
|
|
gap9-models-tiled-doublebuffer-L2 / test-runner-gap9-tiled
Process completed with exit code 1.
|
|
gap9-kernels-tiled-doublebuffer-L2 / test-runner-gap9-tiled
Process completed with exit code 1.
|
|
gap9-kernels-tiled-singlebuffer-L2 / test-runner-gap9-tiled
Process completed with exit code 1.
|
|
gap9-models-tiled-singlebuffer-L2 / test-runner-gap9-tiled
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. 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/
|
|
gap9-models-tiled-doublebuffer-L2 / test-runner-gap9-tiled
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. 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/
|
|
gap9-kernels-tiled-doublebuffer-L2 / test-runner-gap9-tiled
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. 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/
|
|
gap9-kernels-tiled-singlebuffer-L2 / test-runner-gap9-tiled
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. 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/
|