CI (issue_comment) for main #3174
blimlimci.yml
on: issue_comment
!test
/
Permission Check
4s
PR
/
Read CI Testing Configuration
PR
/
Commit Check
Comment
/
Bump metadata.yaml
0s
Tag Bump
/
Check and Update Tag
PR
/
QA CI Checks
!test
/
...
/
Run Config On cherry_pick_from_pr707_into_dev-historical+concentrations
6m 57s
Comment
/
Failure Notifier
0s
!test
/
...
/
Check Repro Result
18s
!test
/
...
/
Clean up test outputs
11s
!test
/
Results
6s
PR
/
Repro Result Notifier
PR
/
Version Bump Check
!test
/
Notify PR of Workflow Failure
0s
Annotations
7 warnings
|
!test / Prepare Command
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 / Read CI Testing Configuration
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/setup-python@v5, GrantBirki/json-yaml-validate@d7814b94473939c1daaca2c96131b891d4703a3c. 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 / Compare cherry_pick_from_pr707_into_dev-historical+concentrations against dev-historical+concentrations / Run Config On cherry_pick_from_pr707_into_dev-historical+concentrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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 / Compare cherry_pick_from_pr707_into_dev-historical+concentrations against dev-historical+concentrations / Run Config On cherry_pick_from_pr707_into_dev-historical+concentrations
Using the prerelease module payu/dev for testing
|
|
!test / Compare cherry_pick_from_pr707_into_dev-historical+concentrations against dev-historical+concentrations / Check Repro Result
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/download-artifact@v4, actions/setup-python@v5. 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 / Compare cherry_pick_from_pr707_into_dev-historical+concentrations against dev-historical+concentrations / Check Repro Result
Running this action via 'uses: EnricoMi/publish-unit-test-result-action/composite@v2 is deprecated! For details, see: https://github.com/EnricoMi/publish-unit-test-result-action/tree/v2#running-as-a-composite-action
|
|
!test / Commit Result
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/download-artifact@v4, crazy-max/ghaction-import-gpg@01dd5d3ca463c7f10f7f4f7b4f177225ac661ee4. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
access-esm1.6-configs-pr714-cherry_pick_from_pr707_into_dev-historical+concentrations-e1aafd2f7bdf4d4f70099dd345f830c638f5682a
|
4.55 KB |
sha256:9e9a6ac8446677b738eacde40049229c8fd9d1f5df6876bb8fd516914316971b
|
|