Skip to content

Handle cache culling and boolean lookup changes in Django 6.2 #3200

Handle cache culling and boolean lookup changes in Django 6.2

Handle cache culling and boolean lookup changes in Django 6.2 #3200

Triggered via pull request June 16, 2026 05:58
Status Success
Total duration 7m 16s
Artifacts 23

test.yml

on: pull_request
Matrix: mysql
Matrix: postgres
Matrix: sqlite
Fit to window
Zoom out
Zoom in

Annotations

10 notices
Coverage
Ending action
Coverage
HTTP Request: PATCH https://api.github.com/repos/django-commons/django-debug-toolbar/issues/comments/4703462100 "HTTP/1.1 200 OK"
Coverage
Update previous comment
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/issues/2385/comments "HTTP/1.1 200 OK"
Coverage
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/pulls/2385 "HTTP/1.1 200 OK"
Coverage
Generating comment for PR
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar "HTTP/1.1 200 OK"
Coverage
Starting action

Artifacts

Produced during runtime
Name Size Digest
coverage-mysql-3.10
61.5 KB
sha256:28c7e2186b4d5799ad43bb7d9e8d7b726ce09b3f3ac355b113a5ac6c7fbfcaa7
coverage-mysql-3.11
63.5 KB
sha256:1d1c48ee528c26566fc25f2261718a028d4a357e03fcb49827fe805aced91de9
coverage-mysql-3.12
126 KB
sha256:dd66ec258e95d5518fc74ebb521d1018ae68c59227cf02667392932471a43c2b
coverage-mysql-3.13
188 KB
sha256:8b97c75582c58d97434f572e74aab59a4b145ecb3ab06e2e56dffeeaf7d399f3
coverage-mysql-3.14
187 KB
sha256:c16165a66c0125f2328eb2a60b4d4f3c875425f9ba79f7162f0aa37f00282637
coverage-postgis-3.10
62.9 KB
sha256:82b91b8a0a5bf8f47dd77a9d992eede510bd978b39c8f0b3cf3fc851a1d0da66
coverage-postgis-3.11
65.1 KB
sha256:64eb163f7f8a10466d031d195877df6bbd3d42bcdcdc5805f0c3093643edf27d
coverage-postgis-3.12
128 KB
sha256:e27514068a08225b30ac27fc888ebc6e2f206888215dbab6e09465f234f4b235
coverage-postgis3-3.13
191 KB
sha256:3ccf146b4c9b3540360d845c2616f2149f2b44810c90d98b0df6d399eac216b8
coverage-postgis3-3.14
189 KB
sha256:1109556a234fba46f9007a203b8396e0bc9ee3f0bf8bc5f487b981e43d6e23ef
coverage-postgresql-3.10
62.8 KB
sha256:dd7ad1c41025b5846e31689a6710bb1144380bba5fb9aae81698b8a0b9ebd4a3
coverage-postgresql-3.11
65.1 KB
sha256:008ec74142d6bb19c4a2ddc5320db4ae0499d68b854baf3e88cd73ca7b5f9e45
coverage-postgresql-3.12
128 KB
sha256:d690c5bdb89e566b9a0c4a87bc7efc2e9ea674b33ee034790ca7252afeb9faf8
coverage-psycopg3-3.10
62.6 KB
sha256:70d2843843b2c78ce0ca1b8c64ed21fe14e2b9252a20884a7ad9527768f01106
coverage-psycopg3-3.11
64.2 KB
sha256:9bc2e3af0c21441a12eec3944c73ad0ce3606e311654464cfec3e4808eb94d6e
coverage-psycopg3-3.12
128 KB
sha256:e6528672698472ce2e8db72ce5f3e728d6371f7127f28749765eafcc87df55f0
coverage-psycopg3-3.13
191 KB
sha256:2d92b3971788cabd822b8961505b81f98707d0bf2b559933909096f4f44ef869
coverage-psycopg3-3.14
189 KB
sha256:ddc875bb1f243033cae024c7e5474d16d83fe3e6fb20c14555aea59c987c621b
coverage-sqlite-3.10
60.8 KB
sha256:39bf82a456273520edde0eee564d3a65336dd276e719f7a6b429d220110cee06
coverage-sqlite-3.11
63.3 KB
sha256:6122eedc8e745d7399bc0985e6878a7494283cffbd5054bc5be22fce9962a095
coverage-sqlite-3.12
126 KB
sha256:f103d7a951203e2025e4292dd4d50563e23f78fcec1af69f52faf69bb47617cf
coverage-sqlite-3.13
188 KB
sha256:0a1048adc6f823bb07d75c7ffd575998bd9750b00fe7601a5a417c97856b6000
coverage-sqlite-3.14
187 KB
sha256:b0da5a54021e1b4e8dc9c4ee963b58686f94ae4382dfec69bb3431c29a037571