[09:50] <tsoome> hi, Im getting (Error ID: OOPS-034f5b0a9d04aa045371d78c3e6d056b) while trying to login qemu bugtracker page.
[09:53] <wgrant> tsoome: Have you logged into Launchpad before?
[09:54] <tsoome> um, sort of — it is able to show me my user info
[09:55] <tsoome> or was it that ubuntu one...
[09:57] <wgrant> Yeah, your account is a little strange.
[09:57] <wgrant> Trying to work out what's happened here.
[09:58] <tsoome> maybe some sort of conversion issue, apparently it is rather old and I had some trouble to recover it, had to use all my connections to get old email re-enabled for that...
[10:02] <wgrant> tsoome: Try now?
[10:03] <wgrant> Hopefully fixed that 13 year old account
[10:04] <tsoome> ou, seems ok. btw, is there still account tsoome?
[10:04] <tsoome> the web interface was hinting there is…
[10:05] <tsoome> thanks btw:)
[10:06] <wgrant> tsoome: Oh, heh, didn't find that one. You can merge it into your main account at https://launchpad.net/people/+requestmerge?field.dupe_person=tsoome
[10:06] <wgrant> If you still have access to the email address.
[10:07] <tsoome> ouch.. that one is even older...
[10:08] <tsoome> in fact, it was my first one from ’93 :P
[10:08] <wgrant> Impressive.
[10:10] <tsoome> well, there are 2 options - either I’ll reuse my other contacts, or if you could change the address there and I’d rather merge the current account with the original one:)
[10:10] <tsoome> other contacts to re-enable my old email address:D
[10:11] <wgrant> tsoome: I can just rename that account out of the way so you can rename your "new" account to ~tsoome
[10:12] <tsoome> yea, i figured that, just that that old email is not working, so I can not get an access right now
[10:12] <wgrant> tsoome: I've renamed it to https://launchpad.net/~tsoome-2 for now.
[11:51] <vila> hi there !
[11:52] <vila> qastaging seems to be in bad shape for ~1 week now, I get timeouts on almost everything :-/ https://code.qastaging.launchpad.net/~vila being the one I'm the most interested in
[15:00] <vila> wgrant, cjwatson: Is qastaging state known (timing out, see above) ? Will it be fixed (if that's on the backseat I can sympathize :-/) ? If not, can you say so (will unblock me) ?
[15:04] <cjwatson> It's known in that I see the same thing too, but I wasn't able to work out what the problem was when I tried last week; the OOPS is mostly non-SQL time, with lots of mysterious long delays between queries
[15:23] <cjwatson> there's an awful lot of /mailinglist requests going on; I wonder if there's a queue that wasn't cleared at the restore
[17:09] <tsoome> wgrant: ping:)
[19:10] <vila> cjwatson: ack (sry noticed late). So once the queue dries things will improve ?
[20:59] <cjwatson> vila: I'm not sure; may need more investigation if/when I can figure out where the logs are ...
[21:00] <cjwatson> and it was just a guess
[21:01] <vila> cjwatson: as long as you don't give up, happy to wait ;-)
[21:01] <vila> Otherwise I'll switch to testing against production... Tests are reliable enough now and should be isolated against a test project anyway
[22:59] <wgrant> cjwatson: Ah, the mailinglist queries would do it.