=== JanC is now known as Guest95859 === JanC_ is now known as JanC === Guest5394 is now known as Laney === pedro_junior_ is now known as pedrinho [12:47] slangasek, thanks for continuing the bisect. It looks like your building the kernels without issue. Just let me know if you need anything. === leitao_ is now known as leitao [16:40] jsalisbury: yeah, I decided with that many iterations it was worth my while to get kernel package building sorted out here for testing ;) I just wish it didn't take me 2.5h for each build iteration [16:42] jsalisbury: also, if I'm reading the git log right, it seems like the bisect is converging on a merge commit for drm-for-v4.14... I'm not sure what happens at that point, I'm guessing we probably /don't/ take the entire 4.14 drm stack into artful [16:56] slangasek, it ought to bisect down the incoming branch too in theory [16:59] apw: ok. so 'git bisect' output telling me "only 2 more steps to go!" is a lie? [16:59] (that's fine, I'd rather it be lying in that direction) [16:59] hmm, it is not clear how it would be totally sure given it has shown a propensity to bisect the other side of a merge [16:59] hmmm [17:00] slangasek, you can also ask bisect to give someone else a log, so they can catch up with your bisect, and build kernels for you [17:00] as 2.5h per kernel is depressing [17:01] apw: I'm not sure if the round trip through jsalisbury beats the 2.5h though, owing to the handoff? [17:01] is possible not [17:01] apw: anyway, the git bisect log is reconstructible from the bug log ;) [17:01] but if you git bisect log it gives the wntire thing as an executable [17:09] slangasek, I'm at the same point you are in the bisect, so just let me know if you want me to build you a kernel at some point. [17:09] jsalisbury: how long does it take you to build one? [17:09] slangasek, about 20 minutes :-) [17:10] jsalisbury: then if you started one now, your build would finish 1h30 before mine - please go ahead :) [17:10] slangasek, I'll kick it off right now. Are you still at 2ce8008711e4837c11e99a94df55406085d0d098 is bad? [17:11] jsalisbury: yes [17:12] slangasek, ok, I'll start a build for 31cb9a8575ca04f47ea113434d4782b695638b62 [17:12] thanks [17:42] slangasek, the test kernel is ready. I put it here: [17:43] http://kernel.ubuntu.com/~jsalisbury/lp1724911 [17:44] slangasek, the fix should be one of these commits: [17:44] https://paste.ubuntu.com/25802899/ [17:46] jsalisbury: sure... almost certainly the giant merge commit listed there for staging ;) [17:47] :) === JanC_ is now known as JanC [17:56] jsalisbury: 31cb9a8575ca04f47ea113434d4782b695638b62: bad [17:56] slangasek, ack. I'll build the next one. [18:09] slangasek, The next kernel is ready for commit 3840ed9548f778717aaab5eab744da798c3ea055. Available from same location. [18:50] jsalisbury: 3840ed9548f778717aaab5eab744da798c3ea055 is bad [19:19] slangasek, ack. I'll build the next one. [19:29] slangasek, Next kernel is ready up to commit 9ea859b11b251df57df5bb9fc146ac014b31071c [20:05] jsalisbury: http://kernel.ubuntu.com/~jsalisbury/lp1724911/ appears to be empty [21:53] slangasek, shoot, I just realized the scp failed. The test kernel should be there now. [21:54] jsalisbury: still shows blank to me [21:54] slangasek, hmm, how about now? [21:55] jsalisbury: there we go :) [22:13] jsalisbury: 9ea859b11b251df57df5bb9fc146ac014b31071c bad [22:17] slangasek, ack. I'll build the next one [22:27] slangasek, the next kernel up to commit 28eb51f7468a43769bd9dca19a54d97ec7a447ed is ready [22:40] jsalisbury: 28eb51f7468a43769bd9dca19a54d97ec7a447ed bad [23:59] slangasek, Next kernel is available up to commit: e63a94f12b5fc67b2b92a89d4058e7a9021e900e