Package: release.debian.org User: [email protected] Usertags: britney (if that's the wrong place, please reassign)
The experimental pseudo-excuses pages are showing many tests as "Test triggered", days after these tests were actually finished and had results on ci.debian.net.
I first noticed this on https://qa.debian.org/excuses.php?experimental=1&package=pandas , where all the amd64 tests were actually finished by the time I used them to write https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141694#10 but many of them still show "Test triggered" now, nearly 3 days later. However, it's probably broader than just that one package: https://release.debian.org/britney/pseudo-excuses-experimental.html currently has over 1000 "amd64: Test triggered", though it was generated at a time when https://ci.debian.net/munin/debian.net/ci-master.debian.net/debci_queue_size.html says the amd64 queue was essentially empty.
This can affect both tests that actually succeeded and tests that actually failed. Affected pages are not totally frozen: they can update to show tests of a newly uploaded version, e.g. pymatgen-core/2026.4.7+dfsg1-7 on the pandas page.
It *probably* doesn't affect the main unstable-to-testing excuses: https://release.debian.org/britney/update_excuses.html has only 20 "amd64: Test triggered".
