[16:17] <ricotz> hello, I am seeing a lot of builds which were successful and have a buildlog, still it wasn't uploaded, but restarted somehow - https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa/+build/24178305
[16:30] <cjwatson> Yes, certain failure modes at the exact wrong time will result in that
[16:36] <ricotz> cjwatson, I guess "cancel and retry" is my only option?
[16:38] <ricotz> so if this is coincidental then I am seeing this a lot :(
[16:54] <cjwatson> ricotz: cancel and retry the build that was already automatically retried?
[16:54] <cjwatson> we have a lot of internal networking issues
[16:55] <ricotz> cjwatson, I did not do anything to this build, it reached this state by itself
[16:56] <ricotz> see the link, the available buildlog shows a successful build, but somehow it restarted "itself"
[16:57] <ricotz> afaict letting this finish will result in a failure of some kind
[16:58] <ricotz> cjwatson, this is a running build which will reach its end soon https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa/+build/24178310
[16:59] <ricotz> maybe it will reach this weird state too
[17:15] <cjwatson> ricotz: I think you are mistaken that letting this finish will result in a failure of some kind.  I'm questioning your "cancel and retry" suggestion because it seems unnecessary.  Just let it run
[17:16] <cjwatson> cancelling and retry will just consume more build farm time for no benefit
[17:16] <ricotz> cjwatson, this one is already in this state and will reach its end soon https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next/+build/24173011
[17:24] <cjwatson> Yes, that's fine
[17:27] <ricotz> cjwatson, see https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa/+build/24178310
[17:27] <sarnold> hello; a pal filing a bug on the linux kernel hit an oops OOPS-c657448eb8ab5ae0f6e1fd6bd9c91be6 "AssertionError: DistributionSourcePackageVocabulary cannot be used without setting a distribution" -- can you suggest if I should ask for a bug report, launchpad question, or just "this is a known weirdness with kernel bug reports"?
[17:27] <cjwatson> ricotz: which is because 2022-07-18 17:23:52+0000 [Uninitialized] twisted.internet.error.ConnectError: An error occurred while connecting: 113: No route to host.
[17:27] <cjwatson> ricotz: not because of the state of the build
[17:28] <ricotz> cjwatson, I am not questioning the state, but the behaviour of launchpad from my POV :\
[17:28] <cjwatson> LP tried several times and gave up after several attempts when the builder was just unreachable
[17:28] <cjwatson> right, and I'm telling you what data I have
[17:28] <ricotz> and I don't see internals ;)
[17:30] <cjwatson> sarnold: Bug report against Launchpad itself, I think.  But it's not clear what your friend was trying to do.  They appear to have been trying to search for a package name while already on /ubuntu/+source/linux/+filebug - they shouldn't have needed to search by that point, since the form would already have been set to the correct package
[17:31] <cjwatson> ricotz: unfortunately this is all at least one level beneath LP, very likely related to networking issues that we're already escalating
[17:31] <sarnold> cjwatson: cool, thanks :)
[17:33] <ricotz> cjwatson, maybe increase the retry number/delay as mitigation?
[17:34] <cjwatson> ricotz: we already did
[17:35] <ricotz> cjwatson, alright
[17:35] <cjwatson> I mean can possibly try harder but at some point it really has to be fixed a level down
[18:39] <ricotz> cjwatson, https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next/+build/24173011 failed as expected