Click-click-click on test retries, trying to be mindful of the test queues (not overloading, nor letting them empty), which I guess was useful useful this week
Reporting issues with test runners and following their status (thanks a lot to @hyask, @andersson123 and @juliank)
Took part in the archive unstucking; in particular but not limited to:
forensics-extra-* which testsuite is only to install all its depends (and recommends?), which is useful for the packager but probably a terrible test at the distribution level: a single issue with Qt and linssid became an opaque error for zlib
report-tracker4/5 for which one test fails and which has blocked dozens of perl packages but the use of all-proposed on all arches makes it difficult to track: Test failures in noble-proposed (all-proposed)
follow-up for the removal of some R packages which are marked as not supporting 32-bit arches anymore: triggered migration-reference/0 test in order to make the revdep test non-regressions
overall, many test retries which have been made much easier by my rewritten excuse page
Discussion with Helmut about the details of abi-compliance-checker analysis and its output
Tabular and predictable layout Status filters! Architecture filters! The date of tests directly visible on the page without hovering over links! Links to the launchpad pages of the tests! Statistics! Re-written status messages that aren’t just API leaks from Britney but actually make sense!