[04:16] <doko> the ppc64el autopkg testers are unhappy: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/a/ansible/20240221_035828_1f136@/log.gz
[08:25] <LocutusOfBorg> A server error has occured, please contact a member of the Ubuntu QA team. You can contact them via the ubuntu-quality mailing list, or via the #ubuntu-quality IRC channel on irc.libera.chat. Traceback: The read operation timed out
[08:25] <LocutusOfBorg> https://autopkgtest.ubuntu.com/request.cgi?release=noble&arch=amd64&package=flask-socketio&trigger=flask%2F3.0.2-1ubuntu1&trigger=flask-socketio/5.3.2-1ubuntu1
[08:25] <LocutusOfBorg> hello, looks like the system asked me to report the issue here :D
[10:20] <Skia> LocutusOfBorg: it seems the test was run anyway? I see a result similar to you request (UUID 96eca963-9399-449f-bfdb-e457172be1ba on https://autopkgtest.ubuntu.com/packages/flask-socketio/noble/amd64)
[10:21] <Skia> also, clicking on you link didn't reproduce the timeout
[10:22] <Skia> (we should probably update that message to include the `q a-help` highlight, btw)
[14:44] <ginggs> any update on ppc64el?
[14:47] <ginggs> dolfin's autopkgtest keeps getting re-queued, even though it succeeded
[14:47] <ginggs> https://autopkgtest.ubuntu.com/packages/d/dolfin/noble/amd64
[14:47] <ginggs> note the different versions in the Versions and Triggers column
[15:10] <ginggs> seems to be happening to ansible as well
[15:10] <ginggs> https://autopkgtest.ubuntu.com/packages/a/ansible/noble/amd64
[15:15] <andersson1234> ginggs: Is britney correctly interpreting the results?
[15:17] <ginggs> andersson1234: they seem to be stuck "Test in progress"
[15:17] <ginggs> i guess because the Version it thinks was run does not match the trigger
[15:17] <ginggs> so it queues it again
[15:23] <andersson1234> ginggs: The last three tests have the same versions no?
[15:25] <ginggs> andersson1234: Version has 2019.2.0~legacy20240219.1c52e83-1
[15:25] <ginggs> but Triggers has 2019.2.0~legacy20240219.1c52e83-1ubuntu1
[15:26] <ginggs> so i think britney requested a test for 2019.2.0~legacy20240219.1c52e83-1ubuntu1
[15:26] <ginggs> but then it can't find a result for that version
[15:26] <ginggs> so triggers it again
[15:59] <ginggs> fwiw, it does not seem to be happening on armhf