[06:53] <oSoMoN> the buildlog for https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/20408925 says the build was successful, yet the build is marked as failed. Is this a known bug, and is there a way to retrieve the build artifacts instead of retrying the build?
[06:53] <oSoMoN> (good morning by the way)
[06:57] <wgrant> oSoMoN: It must have failed to fetch the results for some reason. There's no way to recover the old artifacts, so you'll need to retry the build.
[07:13] <oSoMoN> wgrant, ok, thanks
[10:56] <ral> cjwatson: Some of the launchpad builders have been cleaning for lots of hours. And new jobs don't seem to be being accepted. Would you mind taking a look?
[11:08] <cjwatson> ral: We're in the middle of maintenance - I'll look at it after that
[11:08] <cjwatson> (What you're reporting probably wasn't directly related to maintenance, but regardless, I need to wait until we're done with this move anyway)
[11:10] <ral> cjwatson: Thanks, and no rush I just thought you ought to know.
[11:13] <cjwatson> ral: What jobs aren't being accepted?
[11:14] <ral> Uploads to mosquitto-dev/mosquitto-ppa
[11:14] <cjwatson> ral: OK, that's the maintenance noted in the topic
[11:14] <cjwatson> ral: Unrelated to builders being stuck cleaning, but I've poked those now anyway
[11:15] <ral> Duh, ok, sorry typical not reading the topic.
[11:17] <cjwatson> (However, putting all builders on manual for a short while now while we make sure the new ppa.launchpad.net works)
[11:48] <ricotz> cjwatson, hi, is it expected uploading source packages to PPAs is not working currently?
[11:48] <cjwatson> ricotz: Please see the topic
[11:49] <cjwatson> Looking pretty good, we should be up again soonish, but better to be cautious
[11:49] <ricotz> I known it mentions publishing it disabled
[11:49] <ricotz> *is
[11:50] <cjwatson> Uploads too for part of the time
[11:50] <ricotz> I see, thanks, I will wait patiently :)
[11:52] <cjwatson> ricotz: Should work now
[11:52] <ricotz> cjwatson, thank you
[12:13] <cjwatson> Just dealing with a minor glitch relating to internal signing service connectivity, but publishing should be back up soon
[12:40] <cjwatson> Some ancillary jobs still down, but we're mostly back.
[15:46] <juliank> cjwatson: is git hosting down? fatal: unable to access 'https://<redacted>@git.launchpad.net/~deity/apt/+git/apt/': The requested URL returned error: 500
[15:46] <juliank> from https://launchpadlibrarian.net/511424051/deity-apt-+git-apt.log
[15:47] <juliank> hmm yeah other repos seem inaccessible too
[15:49] <juliank> the answer seems to be yes
[15:49] <juliank> Did I miss an announcement?
[15:49] <tomwardill> it's mid upgrade atm, though I don't think outage is expected
[15:50]  * tomwardill looks
[16:04] <cjwatson> Using SSH will work.  But we're rolling back now
[16:04] <cjwatson> (OK, that's no help for code imports)
[17:02] <cjwatson> juliank: should be fixed (by rollback) now
[18:47] <sbeattie> Hi, is the staging.launchpad.net site supposed to be functional? It doesn't accept existing launchpad users, and, while registering a new user with the staging services appears to work, attmepting to login with it gives an LP oops from the staging site (e.g. OOPS-ee94455d3b2dbabcfc0e853842d21654)
[19:57] <cjwatson> sbeattie: staging login can be ... messy.  best file a support ticket, it may take some effort to disentangle your account
[19:57] <cjwatson> sbeattie: meanwhile for many purposes you can use qastaging instead, which uses production login
[21:34] <sbeattie> cj watson: I did end up going to qastaging instead which mostly worked until I tried to log out whereupon it timed out.
[21:35] <sbeattie> (I had created a test project with the wrong user, which is why I was trying to switch accounts.)