Fixed spurious error when accessing methods during __init__. #621
Triggered via pull request
September 22, 2023 17:17
Status
Success
Total duration
6m 31s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
4 warnings
run-test (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-test (3.11, ubuntu-latest)
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/pull/508/merge, Key: pre-commit-2-eec877cf39ccc99d56dcb4d46bfdfc7fc262f73cba01b278a22e537683b0c6c5-550e99c97865ba2eb967f1d98030f31a18d2cfd2c459950ede7c5282caf8125a, 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-test (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-test (3.9, ubuntu-latest)
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/pull/508/merge, Key: pre-commit-2-204427261e1483f855b2bd9fbcca5cfe7a7f65786053f37503a9be029dff2675-550e99c97865ba2eb967f1d98030f31a18d2cfd2c459950ede7c5282caf8125a, 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.
|