/srv/irclogs.ubuntu.com/2016/11/29/#launchpad.txt

=== chihchun_afk is now known as chihchun
=== JanC is now known as Guest13710
=== JanC_ is now known as JanC
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
rbasakI want to find the last activity on a bug by API. I found the bug_activity collection but don't see a defined ordering. Is there anything that will give me a most-recent-first (such as the bugs collection is defined to do)? Or should I just iterate and sort myself - or do I iterate and not need to sort?13:20
cjwatsonbug_activity is ordered by ID, which should generally amount to most-recent-last13:25
rbasakThanks. So since I can't slice from the end of a collection, I guess I need to iterate anyway?13:27
cjwatsonI'd just iterate; the size is usually not prohibitive.13:28
rbasakOK, thank you.13:29
cjwatsonIn the common case it will fit in a single batch.13:29
rbasakI really like this API BTW. Very nice and straightforward.13:29
cjwatsonIt's rare but nice to get praise for the Launchpad API ;-)13:30
muktupavelscjwatson: do you have time to review merge proposal? https://code.launchpad.net/~mitya57/git-build-recipe/+git/git-build-recipe/+merge/31187413:34
cjwatsonmuktupavels: looks good to me, will land13:41
muktupavelsthanks!13:41
cjwatsonuploaded to Debian unstable, will see about getting it onto our builders a bit later13:49
mitya57cjwatson, thanks!13:58
=== pbek_ is now known as pbek
=== hrybacki is now known as hrybacki|mtg
=== hrybacki|mtg is now known as hrybacki
tsimonq2cjwatson: Ping, I messed up. Kubuntu recently staged a good amount of packages, and we have a script that uses the API to retry the dep waits. So thay ended up triggering 200 some builds before some common deps were ready. Not only did I accidentally flood the queue, but that may be why half of the amd64/i386 builders are disabled, right?16:54
tsimonq2s/flood the queue/flood the queue with builds that are known to fail/16:55
tsimonq2Is the builder thing my fault? If so, I admit to it.16:56
cjwatsontsimonq2: not your fault16:59
tsimonq2cjwatson: Ok, so what's the deal then? :)17:00
cjwatsontsimonq2: lcy01's openstack infrastructure has been having some difficulty and is down for the time being; the rest is certainly worse than usual, but I don't have time to look today, I can just re-enable and hope17:00
tsimonq2cjwatson: Ok fair enough17:01
maprerithe job queue for the amd64/i386 builders is huge.  what's going on?  Also all of lcy01-* is "Cleaning"21:40
naccmapreri: i asked this in #ubuntu-relesae as well -- i think lcy01's openstack is having issues (based upon cjwatson's comment ealier) and there was a glibc and perl5 upload (so a lot of stuff is getting rebuilt?)21:41
maprerioh, I should have really read backlog21:41
maprerinacc: there are no rebuilds for those uploads... (though there they do cause a lot of autopkgtests to be triggered :S)21:41
naccmapreri: err, right, sorry!21:42
naccmapreri: i meant queue entries21:42
maprerinacc: what do you mean by "queue entries"?21:43
naccmapreri: as you said, autopkgtests that need to run21:43
mapreriah yeah21:43
cjwatsonthose don't affect LP builders21:51
cjwatsonthey run on the same cloud but there are quotas21:51
cjwatsonI think the most recent problem was an internal DNS outage that probably took out a bunch of stuff21:52
cjwatsonso we'll see how it goes as that all clears21:52
cjwatsonlooks better already than when I last looked21:52
nacccjwatson: ah ok, thanks for that info (filing it away)21:53
maprericjwatson: well, looking at https://launchpad.net/builders seems lcy01 is still not doing anything :)21:54
* mapreri got used to no build queue at all on launchpad :> guess it's bad idea to get used to such performance21:55
cjwatsonyeah, lcy01 is probably still dead but lgw01 is OK on its own once it's caught up21:57
cjwatsonwhich it should if the resolver quits exploding21:57
maprerithen where would be the fun21:58
acheronukhas been trying to catch up all day, and got not very far with it. hopefully overnight it can22:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!