[04:33] hey, release day today i hope [07:34] https://autopkgtest.ubuntu.com/running only shows one autopkg test running, while there are some dozen in the queue [07:34] also response time, retrying, or just opening the history page for a test takes 10-20 sec [07:46] ack, autopkgtest runners are down right now. should be back up shortly [08:02] back now [09:23] that looks good now, except for the armhf queues [11:44] armhf should also be back [12:35] Skia, what's a cowboy, as in "it's fixed with a cowboy"? C.f. https://bugs.launchpad.net/auto-package-testing/+bug/2083484/comments/5. [12:38] a cowboy, or cowboy patch, is a patch directly on the production system, rather than through the VCS. [12:39] yeehaw [12:40] I guess I'll just add that to my mental image of you and Skia with Stetson hats and spurs. [12:41] https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html shows tests "in progress", but none are running. database glitch again? [12:41] or maybe a queue was flushed? [12:52] Could be the intermittent thing we've mentioned before [12:52] there can be delay between test finish <-> test available in db and on webpage etc [13:01] but these uploads were done yesterday. that should be enough delay? [13:36] can you give links to some example tests so we can have a look? [13:38] https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html, see the "in progress" tests triggered by gcc-11, gcc-12, gdb, llvm-toolchain-18, manila, bind9 [15:03] andersson123: any update? [16:38] sorry, sidetracked, taking a quick look now [16:38] hm, I just had a thought [16:39] we had an outage this morning (something simple, with a simple fix) [16:39] I wonder if maybe we lost a few tests because of that, but I'm very much not sure, looking properly now [17:03] we're EOD'ing now. Will continue looking tomorrow