[12:50] <rtg> apw, I assume this is a duplicate: https://bugs.launchpad.net/bugs/1494562
[12:54] <apw> rtg, yes, will dup
[12:56] <apw> rtg, and done
[12:56] <rtg> apw, ack
[12:57] <apw> rtg, i have sent a proposed fix upstream, and having confirmed it is a 1/256 chance of recurring i have just done a no-change rebuild
[12:57] <apw> until we get confirmation of the approach in my fix
[12:57] <rtg> apw, yup, I kind of figured that out, though I have not seen the patch. Perhaps you could attach it to the bug ?
[13:00] <apw> rtg, attached
[13:00] <apw> rtg, introduced in 3.19 i think so we may see this issue back there also
[13:03] <rtg> apw, gawd, how did you figure this patch out ? it makes my head hurt.
[13:11] <apw> rtg, reading a lot of the history for that file change
[13:12] <rtg> no dobt
[13:12] <rtg> doubt*
[13:13] <apw> rtg, one reason i have not yet applied it, as they may have reasons for that strip and then the fix is to strip it in the signer
[13:13] <apw> not that i can imagine why one would do that, but hey
[13:13] <rtg> hence the no change rebuild
[13:13] <apw> exactly, as there is only a very low change of it recurring on such a build
[13:15] <rtg> apw, do you suppose we can get -10.11 promoted this morning ?
[13:16] <rtg> -7.7 has a weird crash that I'd like to see if it just goes away
[13:17] <apw> rtg, the testig i looked at looked good, bjf do you concur
[13:17] <apw> rtg, and we were waiting on a last few tests to finish
[13:17] <apw> which have been delayed because lcy01 got eaten by juju over night
[13:17] <rtg> again ?
[13:18] <apw> lcy01 is normally broken, but today it is _gone_ same issue as ps4
[13:19] <rtg> I noticed a bunch of test failures on an i386 box, but haven't drilled in to figure it out. everything else looked pretty good.
[13:19] <apw> we have a couple of failures on xfs which seem to be output format changes, which cking is looking at
[13:20] <rtg> there are also a bunch of skylake changes I'd like to get into the wild
[13:20] <apw> otherwise it looked generally sany
[13:20] <apw> yeah i agree we want it out
[13:20] <apw> i think the testing on the previous version was ok, so its not clear it could be any worse
[13:20] <apw> so as soon as the adt tests finish i think it will be migratable
[13:21] <apw> the problematic ones have made happily green
[13:21] <rtg> apw, guess I'll go work un unstable for a bit. 4.3-rc1 is out
[13:21] <apw> ok
[14:01] <bjf> rtg, apw, testing for 4.2.0-10.11 looks good to me 
[14:02] <rtg> bjf, ack. do I just remove the tag for auto-promotion ?
[14:02] <bjf> apw, ^ ?
[14:02] <apw> bjf, if we set the test to good will shanky do that for us now ?
[14:03] <bjf> apw, lets try ...
[14:03] <apw> when it sees all the ADT tests done, which they are not all yet
[14:03]  * apw whips the camels
[14:04] <cking> poor camelids
[14:05] <apw> bjf, ok i am wacking some failed dkms tests
[14:05] <apw> but i think it would be good to see this do the right thing itself
[14:06] <bjf> apw, what exactly did you do? "automated-testing" is already "Fix Released" on the tracking bug
[14:06] <apw> i exactly did nothing, i cirtainly did not move that task
[14:06] <apw> oh are you looking at 10.10 or 10.11
[14:07] <bjf> apw, 10.11
[14:07] <apw> oh and ... of course it would have gotten confused in the old stuff because we only have the 
[14:07] <apw> abi number, so this test of the shanky changes is a bust
[14:07] <bjf> :-)
[14:07] <apw> that is all fixed with the new adt based regression bits
[14:07] <apw> so ... rip the tag and we'll see it migrate when adt passes
[14:08] <henrix> apw: note that shank looks for the test results here: https://people.canonical.com/~kernel/status/dashboard-helper/proposed-migration/regressions.txt
[14:10] <apw> henrix, no you shouldn't be using the adt-matrix that is a human jobbie, proposed-migration is good
[14:10] <apw> now ... why on earth do i not have all the matching results ... in adt-matrix ... grr
[14:10] <apw> henrix, what y9ou have done is right
[14:11] <henrix> apw: right, but i still see regressions in that regressions.txt for which i don't know what to do :)
[14:11] <henrix> apw: there are 3 tracking bugs halted because of these regressions
[14:11] <apw> henrix, give me a minute
[14:12] <henrix> apw: ack, thanks
[14:12] <apw> and i'll have a look and hsow you how i have a look
[14:15] <popey> cking: further to my moan that 4.2 causes slowdown during IO, I'm also finding my laptop is painful when running any kind of hangout / webrtc chat thing - even with nobody else joined, and my webcam off! Very odd.
[14:16] <popey> (may not be a 4.2 thing, but it certainly got very worse recently) (load avg 13 during a hangout, and completely unresponsive desktop)
[14:16] <ogra_> does it grow spikes on the keyboard and stuff ? 
[14:16] <ogra_> or what do you mean by painful ? :)
[14:16] <popey> back under your bridge!
[14:17] <cking> popey, well, I've got 2+ more days of intensive fs testing to complete then I can do a full apples vs pears comparison
[14:17] <popey> heh
[14:17] <apw> bjf, ok leave that tag on there a sec, there is some issue with britney i'd like to get debugged
[14:17] <cking> meanwhile, I'll send you an email with some things to try to get some more hard facts so I can ponder on what's going on
[15:05] <popey> cking: thanks
[16:44] <TJ-> Using 'ecryptfs-recover-private' with 4.2.0-10-lowlatency, getting "Could not find valid key in user session keyring ...", but 'keyctl list @u' shows the keys are present. I've been using this daily for weeks to mount external disk file-systems but today it fails, mount reporting "mount: mount(2) failed: No such file or directory" but both source and mountpoint exist. Any ideas?
[16:45] <cking> tyhicks, ^^
[16:45] <tyhicks> TJ-, cking: I can help in ~15 min
[16:46] <TJ-> tyhicks: no rush... I'm digging into it but drawing blanks so far
[17:01] <om26er> Hi! it seems kernel 4.3 rc1 build failed or something, is that a known issue? if so how long is the build fix expected ?
[17:01] <om26er> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/
[17:05] <tyhicks> TJ-: are you logged into the machine over ssh?
[17:06] <TJ-> tyhicks: No, regular boot session with KDE. The problem FS is an external drive 
[17:06] <TJ-> tyhicks: Can I private you a link URL to a log of the attempt?
[17:08] <tyhicks> TJ-: Sure
[19:13] <smoser> hey
[19:13] <smoser> what is the right way to do what i would have thought this would do:
[19:13] <smoser>  git://kernel.ubuntu.com/ubuntu/ubuntu-wily
[19:13] <smoser> my expectation based on https://wiki.ubuntu.com/KernelTeam/GitKernelBuild 
[19:13] <smoser> showing git clone git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[19:16] <smoser> i'm guessing its 'unstable' 
[19:16] <smoser> based on http://kernel.ubuntu.com/git/ubuntu/unstable.git/
[19:16] <smoser> is that right ?
[19:19] <rtg> smwe've moved wily and unstable to LP, so they've got new paths.
[19:19] <rtg> smoser, ^
[19:19] <rtg> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily
[19:19] <smoser> thanks
[19:19] <rtg> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
[19:20] <smoser> seems someone is maintaining the unstable though at the old location still
[19:20] <rtg> smoser, both should be mirrored to kernel.ubuntu.com in the usual places
[19:21] <smoser> i dont see a wily at kernel.ubuntu.com
[19:21] <smoser> and get:
[19:21] <smoser> ⟫ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git
[19:21] <smoser> Cloning into 'ubuntu-wily'...
[19:21] <smoser> fatal: remote error: access denied or repository not exported: /ubuntu/ubuntu-wily.git
[19:23] <rtg> smoser, apw did it. looks like he put wily in kernel-ppa/mirror
[19:23] <smoser> rtg, are you able to easily confirm or deny a suspicion i have that COMMAND_LINE_SIZE changed in the generic arm64 kernel between vivid and wily ?
[19:23] <rtg> smoser, that sounds familiar
[19:24] <apw> smoser, its master in LP
[19:24] <smoser> well, it seems to have shortened.
[19:25] <rtg> smoser, '#define COMMAND_LINE_SIZE 1024' in both kernels
[19:25] <apw> rtg, we can symlink that kernel-ppa/mirror/ubuntu-wily.git over to ubuntu, i have tested it, you wen't keen
[19:26] <rtg> apw, I'm fine the way it is. 
[19:26] <apw> ok
[19:28] <rtg> apw, at some point we should host all of our git repo on LP and just mirror them to wani
[19:28] <apw> rtg, right that is the plan ... 
[19:28] <rtg> apw, perhaps when we are all in the same room ?
[19:28] <smoser> well, whatever is correct, please update doc ?
[19:29] <rtg> smoser, URL ? (I can't remember it)
[19:30] <smoser> you can't remember from above, where i typed it :)
[19:30] <smoser> https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[19:30] <smoser> thats where i saw it
[19:30] <rtg> ah, smart alek.
[19:30] <rtg> you just think I read for content
[19:30] <smoser> also mentioned here https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide
[19:31] <rtg> apw, so maybe we _should_ just link wily. that way I don't have to edit wiki pages.
[19:31] <apw> rtg, ok ... i'll sort it
[19:33] <apw> rtg, and done
[19:33] <rtg> smoser, does it work for you now ?
[19:34] <smoser> does what work ?
[19:37] <apw> the old name
[19:38] <rtg> smoser,  git clone git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git
[19:43] <smoser> ah.it does