Prek #1301
bckohantest.yml
on: pull_request
Matrix: macos
Matrix: mariadb
Matrix: mysql
Matrix: oracle
Matrix: postgres
Matrix: sqlite
Matrix: windows
coverage-combine
Annotations
29 errors and 27 warnings
|
postgres (3.12, 12, psycopg2, dj42)
The run was canceled by @bckohan.
|
|
postgres (3.10, latest, psycopg2, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.12, latest, psycopg3, dj60)
The run was canceled by @bckohan.
|
|
postgres (3.13, latest, psycopg3, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.14, latest, psycopg3, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.11, 12, psycopg2, dj42)
The run was canceled by @bckohan.
|
|
postgres (3.12, latest, psycopg2, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.14, latest, psycopg3, dj60)
The run was canceled by @bckohan.
|
|
postgres (3.11, latest, psycopg2, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.11, latest, psycopg2, dj52)
The operation was canceled.
|
|
mysql (3.12, latest, mysqlclient2x, dj52)
The run was canceled by @bckohan.
|
|
mysql (3.12, latest, mysqlclient2x, dj52)
The operation was canceled.
|
|
postgres (3.11, latest, psycopg3, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.12, latest, psycopg3, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.11, latest, psycopg3, dj52)
The operation was canceled.
|
|
postgres (3.12, latest, psycopg3, dj52)
The operation was canceled.
|
|
oracle (3.14, dj60, oracle-free:latest)
The run was canceled by @bckohan.
|
|
oracle (3.14, dj60, oracle-free:latest)
The operation was canceled.
|
|
postgres (3.12, latest, psycopg2, dj60)
The run was canceled by @bckohan.
|
|
postgres (3.12, latest, psycopg2, dj60)
The operation was canceled.
|
|
postgres (3.10, latest, psycopg3, dj52)
The run was canceled by @bckohan.
|
|
postgres (3.10, latest, psycopg3, dj52)
The operation was canceled.
|
|
oracle (3.10, dj42, oracle-xe:21)
The run was canceled by @bckohan.
|
|
oracle (3.10, dj42, oracle-xe:21)
The operation was canceled.
|
|
oracle (3.12, dj52, oracle-free:latest)
The run was canceled by @bckohan.
|
|
oracle (3.12, dj52, oracle-free:latest)
The operation was canceled.
|
|
postgres (3.13, latest, psycopg3, dj60)
The run was canceled by @bckohan.
|
|
postgres (3.13, latest, psycopg3, dj60)
The operation was canceled.
|
|
|
|
macos (3.14, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sqlite (3.14, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mariadb (3.14, mysqlclient2x, latest, healthcheck.sh --connect --innodb_initialized, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sqlite (3.10, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sqlite (3.12, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos (3.10, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos (3.12, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.10, 12, psycopg2, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows (3.14, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mariadb (3.12, mysqlclient2x, latest, healthcheck.sh --connect --innodb_initialized, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mariadb (3.10, mysqlclient14, 10.4, mysqladmin ping, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql (3.14, latest, mysqlclient2x, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows (3.10, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows (3.12, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql (3.10, 8.0, mysqlclient2x, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql (3.12, 8.0, mysqlclient2x, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql (3.10, 8.0, mysqlclient14, dj42)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.11, latest, psycopg2, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql (3.12, latest, mysqlclient2x, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.11, latest, psycopg3, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.12, latest, psycopg3, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
oracle (3.14, dj60, oracle-free:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.12, latest, psycopg2, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.10, latest, psycopg3, dj52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
oracle (3.10, dj42, oracle-xe:21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
oracle (3.12, dj52, oracle-free:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
postgres (3.13, latest, psycopg3, dj60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
linux-py3.10-dj42-mysqlclient14-mariadb10.4.coverage
Expired
|
33.7 KB |
sha256:772cdf9ca9ba343ab2dd707c6f6ec85cfe1abc77106521b161f5975a283f5503
|
|
|
linux-py3.10-dj42-mysqlclient14-mysql8.0.coverage
Expired
|
33.7 KB |
sha256:063eb5f73f506eb0c79dbfac6442b2730878fabdbb58b51fe3e3cacda45fed2b
|
|
|
linux-py3.10-dj42-mysqlclient2x-mysql8.0.coverage
Expired
|
33.7 KB |
sha256:7403e097641467aa4aacd27b0507f13574975f00298a1d57b149879a3d4b7b39
|
|
|
linux-py3.10-dj42-psycopg2-pg12.coverage
Expired
|
33.7 KB |
sha256:32e735edd45ca93acb7f236edbe56bc1490441190cc10da99193928e1c8327a9
|
|
|
linux-py3.10-dj42-sqlite.coverage
Expired
|
33.8 KB |
sha256:765ab6815f3281199984390cf0c4ec7431849219fa39d642a8d6797984a43652
|
|
|
linux-py3.12-dj52-mysqlclient2x-mariadblatest.coverage
Expired
|
34.1 KB |
sha256:ec253c8e61a0b4d57cb67a93863eb51071a09a6511612158d0eff322e526ce65
|
|
|
linux-py3.12-dj52-mysqlclient2x-mysql8.0.coverage
Expired
|
34.1 KB |
sha256:2905710905a40ca221802132f512fc5fe5107ee310a6cd22b53b6e3c4e50715a
|
|
|
linux-py3.12-dj52-sqlite.coverage
Expired
|
34.1 KB |
sha256:9999d4c91270105839cc22584891782424722ec817746be854054d138d3b8736
|
|
|
linux-py3.14-dj60-mysqlclient2x-mariadblatest.coverage
Expired
|
30.8 KB |
sha256:662dff59f42b968ce1fade77b71ab452e5af3f0ed2dba981039ca2cd3315b464
|
|
|
linux-py3.14-dj60-mysqlclient2x-mysqllatest.coverage
Expired
|
30.8 KB |
sha256:b0b70281a543c063757a8b30c4722142cb387d6d24948826637136f0c8113988
|
|
|
linux-py3.14-dj60-sqlite.coverage
Expired
|
30.7 KB |
sha256:74018af05afc6237b3d6c0defd711b379ccc25dc2d45ee15339f5de9ff513f55
|
|
|
macos-py3.10-dj42-sqlite.coverage
Expired
|
34.1 KB |
sha256:71826f4bfd47795f1f1257bc05fb502a348a3740315cd7c98dd7fe538f4a69fa
|
|
|
macos-py3.12-dj52-sqlite.coverage
Expired
|
34.3 KB |
sha256:7dfc09663f4e6197178478b340bf64f70e4494d9f816cf4f972212f3d3ec860a
|
|
|
macos-py3.14-dj60-sqlite.coverage
Expired
|
30.9 KB |
sha256:41af13f96320f4cd5ac3e57cc2a776386aeb1a06f4eb4e8126388ef133cf910b
|
|
|
requirements-linux-py3.10-dj42-mysqlclient14-mariadb10.4.coverage.txt
Expired
|
2.21 KB |
sha256:9b43d84cdb83c02bbcf475652d982e7c24018ad2278259a4dd4d5b2360b72ee0
|
|
|
requirements-linux-py3.10-dj42-mysqlclient14-mysql8.0.coverage.txt
Expired
|
2.21 KB |
sha256:bfab96f98e0cc882e5c67762d3b8a1f4cdcb03cc974079a686d1847d4720f5a4
|
|
|
requirements-linux-py3.10-dj42-mysqlclient2x-mysql8.0.coverage.txt
Expired
|
2.21 KB |
sha256:a0eb8c5030e101821c19225bdba8ab4794a2659623a27971d787f3709eaf5694
|
|
|
requirements-linux-py3.10-dj42-psycopg2-pg12.coverage.txt
Expired
|
2.2 KB |
sha256:5f09c92ef22c2eb0db7ac7e1c8d4ffcbf2b18b03eebaac9cc1903e20f999c329
|
|
|
requirements-linux-py3.10-dj42-sqlite.coverage.txt
Expired
|
2.17 KB |
sha256:5b04bc44c507714afa3202344e09e94db0e854ff2c38aa86df01db6fce6dd3df
|
|
|
requirements-linux-py3.12-dj52-mysqlclient2x-mariadblatest.coverage.txt
Expired
|
2.15 KB |
sha256:91d16b9500d0ff368c7280933a3913ce26b1332e73f867ad18258c7da917b797
|
|
|
requirements-linux-py3.12-dj52-mysqlclient2x-mysql8.0.coverage.txt
Expired
|
2.15 KB |
sha256:3ff89322db02c0924ab3fe095dd3be75868c89be71d5657c7564056ec78eac84
|
|
|
requirements-linux-py3.12-dj52-sqlite.coverage.txt
Expired
|
2.1 KB |
sha256:f4adf1029957a95e7960c1934f58518990e86e54f9b806c11acaaee985639b9d
|
|
|
requirements-linux-py3.14-dj60-mysqlclient2x-mariadblatest.coverage.txt
Expired
|
2.15 KB |
sha256:d62814b88d801730dc300f336e7d3ca1641646acdca1a8940e7c67981acb4215
|
|
|
requirements-linux-py3.14-dj60-mysqlclient2x-mysqllatest.coverage.txt
Expired
|
2.15 KB |
sha256:736373fa4f9af791c67454e1bd8d14dc48324b17ca1172a31b82149b714a100d
|
|
|
requirements-linux-py3.14-dj60-sqlite.coverage.txt
Expired
|
2.1 KB |
sha256:54f0b9cf9ecf079becacb856a05b843118c2baabab8c899b778cb41375d3b05c
|
|
|
requirements-macos-py3.10-dj42-sqlite.coverage.txt
Expired
|
2.17 KB |
sha256:3fa9ef5ea80ffa5a746c41619289b85968c30d9f75a01ceb6229096cdf66d167
|
|
|
requirements-macos-py3.12-dj52-sqlite.coverage.txt
Expired
|
2.11 KB |
sha256:b1ee49cbed11c61b0659aab2c746abf1d23effe5092244b17de26e8c22dc3015
|
|
|
requirements-macos-py3.14-dj60-sqlite.coverage.txt
Expired
|
2.11 KB |
sha256:1d968cc386766642ac84b8e9954a08ff564ce5c6b3ee435254f016b6cb0b24d2
|
|
|
requirements-windows-py3.10-dj42-sqlite.coverage.txt
Expired
|
2.24 KB |
sha256:43d63e99f4d66acab2d3ba567e61957a2553c492b204744d27ac8455661cbfb4
|
|
|
requirements-windows-py3.12-dj52-sqlite.coverage.txt
Expired
|
2.18 KB |
sha256:aad2088cefd5e9fac8507216b75cf876c1cbeb8a0255357b16f614cc687fa051
|
|
|
requirements-windows-py3.14-dj60-sqlite.coverage.txt
Expired
|
2.17 KB |
sha256:729256ce639ff83125bd0227a5a61df30a90062fc3aa41d477d14ed9e9d09380
|
|
|
windows-py3.10-dj42-sqlite.coverage
Expired
|
33.9 KB |
sha256:f481e4cadcc708d2c2c4fefff6afb7c93b0b06e542e95dae197f44ff074eb06f
|
|
|
windows-py3.12-dj52-sqlite.coverage
Expired
|
34.3 KB |
sha256:91a140337216097d7461cef2708bef20d2635dd5f1ecca551a0da4d8b16d3108
|
|
|
windows-py3.14-dj60-sqlite.coverage
Expired
|
30.9 KB |
sha256:ed1c371e90cde22c108e8462931324102847785871f0f99e243c074947990c17
|
|