Skip to content

Create run_tests.yaml #637

Create run_tests.yaml

Create run_tests.yaml #637

Triggered via pull request August 28, 2024 00:47
Status Success
Total duration 1h 36m 10s
Artifacts

run_tests.yml

on: pull_request
Matrix: run-tests
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
run-tests (3.11, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run-tests (3.11, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run-tests (3.11, ubuntu-latest)
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/501/merge, Key: pre-commit-2-9ebbeec5ed28586f145b2f0cc247f998c8a0ed9a771e98ed23505d12fdd8cc04-14cf90c4483adae3737fb4006a4f6e912f944eda1eead41785d01b4130f91468, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.
run-tests (3.9, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run-tests (3.9, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run-tests (3.9, ubuntu-latest)
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/501/merge, Key: pre-commit-2-bc46ef7a21d1eec3d4a4c41467b4f857c1e528c9f5f0965d8bb7ec8cfce2c902-14cf90c4483adae3737fb4006a4f6e912f944eda1eead41785d01b4130f91468, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.