[01:54] bedtools adt run is odd -> requested to test src+binary version 2.19.1-1, jenkins executes source 2.17.0-1 which doesn't have adt tests. [01:55] similar issue with epsilon. [01:57] ipset [02:02] haha retry does not help, it retries old version again none-the-less... [07:16] should daily iso' [07:16] s be spinning again now? [07:17] i.e. for Ubuntu GNOME [07:17] cjwatson, infinity, stgraber ^ === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [12:56] darkxst: Not yet. === mapreri_ is now known as mapreri [21:49] darkxst: No, we'll probably try turning them on tomorrow (assuming the livefs chroot creation ticket got resolved; haven't checked) [21:57] cjwatson, ok [21:59] wgrant: Could you switch http://qa.ubuntuwire.com/ftbfs/ over to utopic when you get a chance? [22:03] cjwatson: It's not resolved yet, AFAIK. [22:03] cjwatson: Also, if you're around, do you happen to know a workaround for britney losing its mind over massive recursive sets? [22:03] AIEEE: counter overflow: 7309 involved packages. [22:03] AIEEE triggered by: libav [22:03] That sort of thing. [22:05] I don't [22:05] You could block stuff until it's all ready per a transition tracker ... [22:05] Then at least probably only the last run will take forever [22:06] Oh, kay, so this doesn't end up being a failure to process things, it's just telling me it hates me? [22:06] Blocking the three problematic packages for now would be simple. [22:06] gst-plugins-bad1.0, libav, rtmpdump [22:07] Let's try that for now and revisit in the $later. [22:07] Yeah, I don't understand it properly but I think the effect is that it gives up on some paths and then spends $forever backtracking [22:08] But it doesn't actually cause a failure directly [22:08] I expect xnox will yell at me later about blocking one of his transitions, but we'll sort that out in a bit. [22:08] However it does tend to cause p-m runs to take hours, so it's best avoided [22:09] infinity: cjwatson: do block libav, and portions of ghc. [22:10] they can be easily worked of a tracker. [22:10] ghc doesn't usually cause counter overflows? [22:10] i think it's something else though, libraw or some such? [22:10] cjwatson: Oh yeah, I should do that. [22:10] infinity: do it as a bug, that way anybody can cancel it once ready. [22:10] xnox: It's the three I mentioned. [22:11] xnox: I'll babysit ghc as usual, I imagine; it shouldn't need blocking [22:11] infinity: yeah, block, there are logs to see past runs anyway to figure out what needs doing. [22:12] cjwatson: Any cleanup need doing if one kills britney mid-run? [22:12] Cause I'm sick of waiting on this one to finish. :P [22:12] infinity: Shouldn't be [22:12] Oh, it might be near done anyway. [22:13] They've been ~4h each since this started, and this is 2.5 in... [22:13] Err, 3.5 [22:13] Meh. [22:13] Screw it. Killing. [22:20] Oh, there were a few other triggers too. Bother. [22:21] They might be enough smaller than libav not to matter as much [22:21] AIEEE: counter overflow: 3217 involved packages. [22:21] AIEEE triggered by: openjpeg [22:21] Still seemed pretty big. :P [22:22] I've just blocked every trigger for now to see if that happies things up, then we can peel back the damage. === Ursinha is now known as Ursinha-afk