 done some retries of what I can see
 just libreoffice and qtox really now after my retries eariler
 samplv1 seems to have maged to regress itself I think
 I have uploaded NMU for qtox a few minutes ago, will be auto-synced closer to the end of day
 :)
 I have also done some retries for qtsvg and pyqt5 today.
 I have retried libreoffice test against the single trigger of qtbase, and they are running. I am not sure if that is the best tactic, or if fewer tests against multiple triggers is better. one with multiple seem to be failing a lot
 If it helps qtbase to migrate then I think it's correct tactic :)
 lets see what my tests do then
 We probably also need a retry against -gles?
 I was waiting to see what the non gles ones do
 Right, that makes sense
 also on some arches where runners are lxd, too many libreoffice tests running seems to cause issue. e.g. timeouts and running out of space
 (Photo, 1193x574) https://i.imgur.com/8wEyHoI.jpg
 looks hopeful!
 triggering similar for -gles
 oooh. samplv1 passed on armhf 😀
 Great!
 Retried pyqt5 tests with dbus-python from proposed, that should help with `No module named '_dbus_bindings'` with python3.9
 Also retried software-properties tests, python-apt 2.1.3ubuntu3 which migrated to release today should fix them.
 So far no idea about pyqt5chart/i386 and sasview/arm64. Retried them with all-proposed=1, maybe that changes something.
 pyqt5chart does not have an i386 build
 Yes, but the previous tests somehow passed with all packages from amd64
 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/i386/p/pyqt5chart/20201027_230143_fc8df@/log.gz — but I have little knowledge of how cross-testing works
 no idea. lol
 [18:23] adsb has changed the topic to: Broken: dinstall | welcome new DDs: deller, jvalleroy … [18:23] <adsb> td: dinstall is unhappy
 @mitya57 so I don't think launchpad will see qtox tonight to sync
 can't manual sync either obviously