Skip to content
CI

Remove comm hash and add per-comm caches #595

Sign in to view logs

Remove comm hash and add per-comm caches

Remove comm hash and add per-comm caches #595

Triggered via pull request August 23, 2024 18:35
@JDBetteridgeJDBetteridge
synchronize #724
JDBetteridge/remove_comm_hash
Status Success
Total duration 21m 45s
Artifacts –

ci.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 48 notices
test (3.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.12)
test (3.12)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.10)
test (3.10)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.9)
test (3.9)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]
test (3.11)
test (3.11)
or: ssh -i <path-to-private-SSH-key> [email protected]