Skip to content

Merge pull request #22 from olivierdalang/remove-autoreload #255

Merge pull request #22 from olivierdalang/remove-autoreload

Merge pull request #22 from olivierdalang/remove-autoreload #255

Triggered via push December 4, 2023 10:49
Status Success
Total duration 2m 52s
Artifacts

test.yml

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

Annotations

23 warnings
Tests dj4.1 / sqlite / py3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.1 / sqlite / py3.8
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.1 / sqlite / py3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.1 / sqlite / py3.11
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj3.2 / sqlite / py3.10
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj3.2 / sqlite / py3.10
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.2 / sqlite / py3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.2 / sqlite / py3.8
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj3.2 / sqlite / py3.6
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.2 / sqlite / py3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.2 / sqlite / py3.11
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj3.2 / postgres / py3.10
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj3.2 / postgres / py3.10
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.1 / postgres / py3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.1 / postgres / py3.11
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.1 / postgres / py3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.1 / postgres / py3.8
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.2 / postgres / py3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.2 / postgres / py3.8
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj3.2 / postgres / py3.6
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj3.2 / postgres / py3.6
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.
Tests dj4.2 / postgres / py3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/action@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests dj4.2 / postgres / py3.11
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-f71d82dceb30f97b09ae83a8bd4c83b719d6796fbf4056ed9723d3827f9b82ec, 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.