Skip to content

Merge pull request #28 from olivierdalang/optimise-admin #280

Merge pull request #28 from olivierdalang/optimise-admin

Merge pull request #28 from olivierdalang/optimise-admin #280

Triggered via push March 4, 2024 16:13
Status Success
Total duration 3m 4s
Artifacts

test.yml

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

Annotations

35 warnings
Tests dj4.2 / sqlite / py3.11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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 dj3.2 / sqlite / 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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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.8
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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.2 / postgres / py3.11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pre-commit/action@v2.0.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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-05f9ca054ebaa26ed0f23e500e15af3c0d8557a7992d44e5f0cead09d8244df6-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.