/srv/irclogs.ubuntu.com/2016/10/05/#ubuntu-devel.txt

naccmwhudson: probably my own ignorance but why would alignment and parallelism interplay like that? or is parallelism a red herring?00:35
sarnoldre-run locally with -j4 or re-run on the arhmhf with -j1 to find out? :)00:37
naccsarnold: so on the armhf porter, -j1 is used and it passes00:38
slangaseknacc: the porter box's kernel does not raise SIGBUS00:38
naccsarnold: but on the test rebuild, -j4 was used and it failed00:38
naccslangasek: ah00:38
naccgood info! :)00:38
slangasekso parallel is a red herring00:38
sarnoldslangasek: wow, how (and _WHY_)? :)00:38
slangaseksarnold: the better question is, why did the armhf builders start raising it00:39
sarnoldeach arch has their own rules.. it feels to me like the builders ought to stick with 'usual'00:39
slangaseksarnold: the usual is to not raise SIGBUS on anything armv7 or later.  But android kernels forced it on, so we used to get bugs that were not reproducible on the builders or porter box, only on phones00:40
slangasekthen when we moved builders to armhf guests on arm64, suddenly we were getting sigbus there, but I don't think anyone's been able to determine why00:40
slangasekif we could get the porter box to also have it on, we'd be golden00:40
naccslangasek: mwhudson: i guess i'm at a loss on how to go further with the memcached failure then, given that i can't reproduce it (at least, not that i know of yet)00:41
sarnoldyeah, inconsistent seems like a quite route to insanity00:41
slangaseknacc: mwhudson's hint (not validated yet by me) is to log into the armhf chroot on the arm64 porter box00:41
naccslangasek: interesting, I can try that tomorrow!00:41
naccslangasek: would you happen to know who i might turn to for llvm testcase failures?00:42
nacc(unrelated to arm)00:42
slangaseknacc: perhaps doko00:43
naccheh ok :)00:43
=== robertm___ is now known as remanos
pittiGood morning05:26
cpaelzernacc: coreycb: I already was on a birthday overloading my belly at the time yesterday :-/05:41
cpaelzercoreycb: I'm here to help you get access to our node as interim help if you want that, but you'll need some extra access I'll send you in a query05:41
cpaelzercoreycb: I think jamespage and beisner were of your Team and could share one where you already have VLAN access05:42
cpaelzercoreycb: but we can discuss all that once you are online again05:42
cpaelzercoreycb: and in any case if I'm not here jfh might be able to help as well (but same TZ)05:42
cpaelzerah - and good morning devel channel :-)05:42
pittiroaksoax: you are double sure that you want to replace the stable MaaS 2.0 with a beta version of 2.1 a week before release? the upload does not point to a FFE bug, so please reupload with a pointer to that, so that this can be discussed somewhere (and/or discuss in #u-release)05:57
pitticoreycb: can you please have a look at the failed armhf/s390x tests of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#nova ? they complain about compute-kvm not running, which is understandable in an lxc container06:40
pitticoreycb: so this is a regression between b2 and rc206:41
sil2100xnox: hey! Any news on the upstart merge and new release?08:10
doko_caribou: is https://bugs.launchpad.net/ubuntu/+source/tomsfastmath/+bug/1619239 still in progress?08:24
ubottuLaunchpad bug 1619239 in tomsfastmath (Ubuntu) "[MIR] tomsfastmath (runtime dependency of clamav)" [High,In progress]08:24
cariboudoko_: we've postponed it until 17.04 & I have prepared a new clamav w/o the tomsfastmath dependancy that is about to be uploaded08:25
doko_ta08:26
cariboudoko_: the security team's backlog for MIR reviews made it almost impossible to have it reviewed for 16.1008:26
doko_Mirv: that looks like a qt issue: https://launchpad.net/ubuntu/+source/ubuntu-push-qml/0.1+15.10.20150826.1-0ubuntu2/+build/1099092308:28
Mirvdoko_: ack, so it does08:43
dpmpopey, doko_, has bug 1625074 been sorted out?09:31
ubottubug 1625074 in ubuntu-terminal-app (Ubuntu) "[MIR] ubuntu-terminal-app" [High,New] https://launchpad.net/bugs/162507409:31
doko_dpm, popey: wait for review from the security team09:33
dpmdoko_, ok, thanks, it seems they say review is underway09:36
popeywillcooke: ^ I think you mentioned some new info from the security team?09:37
* willcooke reads09:37
willcookeso yeah, we have the OK to go ahead with MIRing before the security review is complete09:37
willcookedoko_, I'll ask slangasek to confirm with you formally09:38
rbasakddstreet: please could you do the SRU paperwork for bug 1224007?10:22
ubottubug 1224007 in vlan (Ubuntu) "mtu not always set properly on bond/vlan interface" [Medium,Confirmed] https://launchpad.net/bugs/122400710:22
=== hikiko is now known as hikiko|ln
jbichaLocutusOfBorg: the link-grammar autopkgtest failure was my fault but it's all fixed now11:21
=== hikiko|ln is now known as hikiko
=== dholbach_ is now known as dholbach
caribounacc: did you find anything regarding the llvm-3.6 FTBS so far ?12:19
stgraberinfinity: are you planning on refreshing the yakkety chroots pre-release? working on crappy internet today (aka LinuxCon) and just noticed it's pulling quite a lot of updates12:30
coreycbpitti, I'll take a look, I thought I'd fixed it yesterday but perhaps not12:31
LocutusOfBorgcaribou, can I know the llvm issue context?12:36
LocutusOfBorgjbicha, thanks12:36
caribouLocutusOfBorg: the FTBS is very early in the rules file:12:37
cariboudpkg-query: no packages found matching g++-6.112:37
cariboudpkg: error: --compare-versions takes three arguments: <version> <relation> <version12:37
caribouLocutusOfBorg: just not sure if nacc has identified the issue already12:38
LocutusOfBorgI know what the issue is12:40
LocutusOfBorgand I know what the patch is12:40
LocutusOfBorgusually asking me about llvm issues is a quickeer fix12:41
caribou:)12:41
LocutusOfBorgyou just need to adjust the regex for new gcc12:41
caribouLocutusOfBorg: yeah, that was my next step12:41
caribouLocutusOfBorg: nacc told me about the FTBS since clamav which I uploaded is its only dependancy12:42
LocutusOfBorghttps://anonscm.debian.org/viewvc/pkg-llvm/llvm-toolchain/branches/3.8/debian/rules?r1=2038&r2=204112:43
LocutusOfBorgI want to get rid of old llvm in Debian and Ubuntu12:43
caribouLocutusOfBorg: thanks; do you want me to take care of it or you want to do it yourself ?12:44
LocutusOfBorgwhy aren't you using llvm 3.8 is unknown to me12:44
LocutusOfBorgcaribou, ENOYETCOREDEV12:45
caribouLocutusOfBorg: oh, didn't know that12:45
LocutusOfBorgand I want to get rid of that12:45
* LocutusOfBorg applied for core-dev but only one advocacy so far12:45
caribouLocutusOfBorg: & Debian is still using 3.6 and from what I can gather, clamav needs sensible adaptation to use higher than 3.612:45
caribouLocutusOfBorg: & I don't have much to do about it myself, I just merged the package from debian12:46
LocutusOfBorgwell, yesterday Sylvestre started the transition to llvm-3.812:46
LocutusOfBorgso I suspect clamav being broken in Debian right now?12:46
* LocutusOfBorg does some dak query 12:46
LocutusOfBorghttps://buildd.debian.org/status/fetch.php?pkg=clamav&arch=amd64&ver=0.99.2%2Bdfsg-3%2Bb1&stamp=147562117212:47
LocutusOfBorgsigh, true12:47
caribouLocutusOfBorg: ok, I'll wait until nacc comes in so we don't overlap on this12:47
LocutusOfBorgconfigure: error: LLVM < 3.7 required, but "3.8.1"(381) found12:48
caribouyep, that's what I got yesterday when I tried to build with 3.812:48
LocutusOfBorgok let me fix llvm 3.612:49
LocutusOfBorgsigh12:49
caribouLocutusOfBorg: don't bother, I can do it12:51
LocutusOfBorgthanks12:54
LocutusOfBorgif you want to forward patches to the debian bug reports... :)12:54
LocutusOfBorgeven if trivial, I can give you credits and maybe upload12:54
LocutusOfBorg(having RC bugs helps in kicking them out of testing)12:54
caribouLocutusOfBorg: wait, are we talking about the same thing ? I was referring to applying your regex modification to LLVM-3.612:58
LocutusOfBorgyes13:00
caribouk, I'm on it13:00
LocutusOfBorgcore-devs: syncpackage -s costamagnagianfranco portaudio1913:01
LocutusOfBorgplease ^^13:01
LocutusOfBorgpatch for this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83395013:01
ubottuDebian bug 833950 in portaudio19 "libportaudio2: brltty-espeak stops working with libasound2 1.1.2-1" [Serious,Fixed]13:01
LocutusOfBorgdholbach, ^^13:03
LocutusOfBorgthis is a serious bug that prevents blind people from using the system13:04
dholbachin a all right now13:06
dholbachsorry, in a call13:10
LocutusOfBorgI aksed ginggs to sync, I can open a bug if needed13:11
* LocutusOfBorg TIA13:11
=== _salem is now known as salem_
=== imcleod_ is now known as imcleod
pittiapw: I finally got an useful log, filed bug 1630578 about the eternal retry loop13:16
ubottubug 1630578 in autopkgtest (Ubuntu) "broken kernel causes eternal test retry loop" [High,In progress] https://launchpad.net/bugs/163057813:16
dholbachLocutusOfBorg, done13:18
LocutusOfBorg<313:18
dholbachit will be sitting in the release team queue13:20
pittiLaney: yay, armhf beat x86 this morning's queue run! (second after s390x)13:34
Laney\o/13:34
LaneyIntel better be worried13:35
ogra_intel is doomed (since yaears !)13:35
LocutusOfBorgdholbach, thanks13:37
dholbach:)13:37
LocutusOfBorgblind people should appreciate that13:38
pittiapw: and I reduced the reproducer from 5:30 hours to 1s, which is a lot more comfy :)13:38
apwpitti, yay :)13:59
=== JanC is now known as Guest96823
=== JanC_ is now known as JanC
caribounacc: I'm about to upload a fixed llvm-toolchain-3.614:57
rbasakcyphermox: is grub2 2.02~beta2-36ubuntu3.4 in the Xenial queue supposed to supersede 2.02~beta2-36ubuntu3.3 in proposed? They refer to the same bug, but the earlier version is still v-needed.15:24
nacccaribou: great!15:25
nacccaribou: thank you15:25
caribounacc: well, you can thank LocutusOfBorg15:26
caribounacc: want me to upload clamav along with it ?15:26
nacccaribou: ah that won't fix it though15:26
naccthe regex fix?15:26
nacci sent that to debian already, or acked the one they had in their bug report15:26
naccit will still fail to build clamav15:26
naccerr, not clamav, but its own testcase15:26
naccthere are two failures15:26
caribounacc: oh, I didn't get that far, the build just killed my test server15:27
nacccaribou: yeah, i didn't want to upload a partial fix, sorry -- i thought i had mentioned that to you earlier15:28
caribougrrr15:28
nacclet me find the test failures15:28
caribounacc: nope but no worry, I had a bit of time so I thought I'd give it a look15:29
nacchttp://paste.ubuntu.com/23280288/15:29
naccare the two failures i see with the regex fix15:29
Odd_Blokepitti: I've noticed that /var/log/syslog ends up with the first N messages with the same (later-than-boot) timestamp whereas journalctl has different, earlier timestamps for the same events.15:30
Odd_Blokepitti: Shall I file a bug for this?15:30
caribounacc: then maybe LocutusOfBorg can help more than I can15:30
pittiOdd_Bloke: I suppose rsyslog records the dates when it receives the event, not the date from teh original event?15:31
pittiOdd_Bloke: rsyslog actually has a mode to pull from the jouranl (which should preserve origianl timestamps), but we don't use that yet; at some point we should as it will also avoid truncated logs on bursts15:31
LocutusOfBorgcaribou, where are the failures?15:31
LocutusOfBorgon i386?15:32
Odd_Blokepitti: Yeah, that rsyslog hypothesis seems likely.15:32
caribounacc: ^^15:32
naccLocutusOfBorg: http://paste.ubuntu.com/23280288/15:32
naccLocutusOfBorg: that occurs on amd64, not sure if the same tests fail on other archs yet15:32
cyphermoxrbasak: yes15:40
LocutusOfBorgnacc, link?15:42
=== acheronuk_ is now known as acheronuk
naccLocutusOfBorg: just provided? http://paste.ubuntu.com/23280288/15:43
LocutusOfBorgnot helping, I want a full build log15:43
LocutusOfBorge.g. a ppa build15:43
naccLocutusOfBorg: would my local sbuild's full log be sufficient?15:44
LocutusOfBorgagainst yakkety?15:44
naccyes15:44
naccwith the fix for the regex15:44
LocutusOfBorgregex fix for llvm 3.6 against yakkety and nothing more15:44
naccyes15:44
LocutusOfBorglet me upload on my ppa15:44
nacci have the same15:44
naccLocutusOfBorg: http://termbin.com/j43515:46
naccLocutusOfBorg: only change to the package was the regex fix for recognizing gcc 615:47
naccbah seems cutoff15:47
rbasaknacc: do you have SRU paperwork for bug 1575543 please?15:51
ubottubug 1575543 in loganalyzer (Ubuntu Xenial) "loganalyzer not work in ubuntu 16.04" [High,In progress] https://launchpad.net/bugs/157554315:51
naccrbasak: was on my list to do today and upload15:52
nacci was fixing it live with a  requestor in #ubuntu yesterday15:52
rbasakSeems to already be in the queue?15:52
naccbah, i thought i had *not* yet uploaded, let me fix the bug15:52
rbasakBut sure, it can be processed when you're ready :)15:52
naccrbasak: updated15:56
rbasakThanks!15:56
naccrbasak: thank you!15:59
juliankeww, autopkgtest had an autopkgtest failure on amd64 for apt/1.3.1. I retried that now, let's see if it goes normally this time16:03
naccmwhudson: slangasek: fyi, reproduce the memcached failure on arm64 porter in armhf chroot16:08
=== grumble is now known as ghostle
naccmwhudson: http://paste.ubuntu.com/23280567/16:10
slangaseknacc: nice, now you have something you can gdb :)16:17
rbasakjamespage: what's the regression risk for the SRU in bug 1608934? Please could you fill that in?16:18
ubottubug 1608934 in Ubuntu Cloud Archive mitaka "ephemeral/swap disk creation fails for local storage with image type raw/lvm" [High,In progress] https://launchpad.net/bugs/160893416:18
naccslangasek: yep :)16:18
naccmwhudson: slangasek: http://paste.ubuntu.com/23280630/ (gdb bt)16:25
naccwill try and debug :)16:25
naccLocutusOfBorg: able to reproduce?16:32
LocutusOfBorgsorry will try now16:38
naccLocutusOfBorg: np, I can also e-mail you the log (as I think it'e exceeding the pastebin's size)16:39
lamont[  OK  ] Reached target Shutdown.16:53
lamont[  397.076385]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4294988998, last ping 4294990256, now 429499155216:53
lamontWHY do we still want to talk to the root fs after we get to shutdown?16:54
lamont(it's trying to reboot...)16:54
koikecyphermox, hey, shim was rejected by debian because of missing copyrights attributions, I just send you a merge proposal, could you take a look when you have some time please?17:11
smoserpitti, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/o/open-iscsi/20161005_154808@/log.gz17:14
smoserwhy would we not have access to kvm there?17:14
slangasekdoko_: did you see that your tomcat8 sync brought a new dep with it (taglibs-standard)?17:21
cyphermoxkoike: ack, but I'll merge that with some changes, we have a shim pending upload now...17:26
koikecyphermox, ok, thanks17:26
slangasekcyphermox: maybe I should merge in the packaging changes that I was making for Debian17:27
slangasekcyphermox: i.e. maybe you want to hold off on work for a bit so I can stop having to redo my changes to debian/copyright ;)17:27
lamontpitti: you around?  I'm trying to fathom what systemd et al might be dowing after "Reached target Shutdown" that requires the root disk still17:29
lamontor how to get a working getty at that point. :/17:30
lamonts/getty/shell17:30
koikeslangasek, ops, I hope I didn't cause a double work here17:31
slangasekkoike: don't worry; my changes are just fixing the order of stanzas in the file17:31
cyphermoxslangasek: ok17:33
=== fginther` is now known as fginther
=== davmor2_ is now known as davmor2
=== ghostle is now known as grumble
pittilamont: did you try booting with systemd.debug-shell? (should be on Ctrl+Alt+F8)18:58
lamontpitti: you're assuming I have more than ttyS119:00
lamontthat's all I have19:00
pittiah, difficult then; after that there's little room for getty etc.; nothing should run then except /lib/systemd/systemd-shutdown, which essentially just umounts root and tells the kernel to power off19:01
pittibooting with "debug console=ttyS1" might still help a bit19:02
naccslangasek: so memcached's configure script has a check to determine if it needs to do alignment or not, but it passes -O2 to the test compilation, which leads to a successful test of the program. If I manually pass no optimization flags, the test correctly raises a SIGBUS. Thoughts?19:32
slangaseknacc: on a Linux system, messing around with possibly /not/ aligning is a waste of effort; there are various cases where the build and runtime behavior can be legitimately different, and even if the test succeeds it's an inefficiency in CPU and/or kernel to do the fix-up on userspace's behalf19:34
slangaseknacc: just neuter the test and always choose to align19:35
naccslangasek: ok, i'll test that -- probably worth sending upstream too then?19:35
slangasekthe test succeeding or failing with different optimization levels is interesting, but not predictive19:35
slangaseknacc: IMHO yes19:35
naccslangasek: ok, thanks!19:35
slangasekmaybe they have users on other platforms who wouldn't like alignment to be enforced, but I don't know what those are19:36
naccslangasek: is this the wrong way to go about it? the build succeeds with this patch, and afaict, there is no configure flag i can pass to say force alignment http://paste.ubuntu.com/23281367/19:47
naccoh i might not need to patch configure.ac anymore19:48
slangaseknacc: that's what I would look to do19:48
slangasek(though I would patch configure.ac and make sure the package used dh_autoreconf for configure)19:49
naccslangasek: yeah, i think it used to -- but there are changelog entries indicating memcached doesn't play properly with dh_autoreconf19:49
nacci'll try and investigate that19:49
naccslangasek: ah ok, i misread the changelog, so just patching configure.ac is sufficient19:53
naccjgrimm: --^ thanks to slangasek's help, memcached's ftbfs is fixed, so i think -server is now clean (pending another test rebuild for the remaining packages, and hopefully LocutusOfBorg figuring out llvm-toolchain-3.6). coreycb, I'm assuming you've got a handle on nova still?20:02
jgrimm:) nice. thanks nacc20:02
coreycbnacc, yep, I've got nova20:04
nacccoreycb: great, thanks for confirming20:04
juliankI'm starting preparing the apt 1.2.15 update for xenial. It's gotten a bit large, it really should have been 3 to 4 updates, but 1.3 development was too busy. Sources for RC1 are available at https://launchpad.net/~deity/+archive/ubuntu/apt-1.2 - binaries should get building soon20:16
juliankThe 1.2.15 update will fix the autoremoval code to only consider the latest provider of a given source package for protecting, so older kernels can effectively be removed even if some of their provides are being depended upon by other packages.20:17
juliankIt also fixes a ton of other bugs and buffer overflows and maybe underflows20:18
juliankOverall, I cherry-picked 54 commits since 1.2.1420:18
juliankFeedback is appreciated. I'll put this on my server-playing thinkpad once the PPA is built and give it a drive for a few days20:20
LocutusOfBorgnacc, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/6984130/+listing-archive-extra20:45
LocutusOfBorgcan't reproduce20:46
juliankkirkland: I'm playing around with byobu and wondering if there's a way to make it automatically pick the last session when starting, as asked in http://askubuntu.com/questions/798763/how-to-make-byobu-automatically-select-last-used-session21:25
=== salem_ is now known as _salem
slangasekcoreycb: looks like nova autopkgtests still fail on armhf and s390x?21:58
slangasekif nova's systemd units are relying on timeouts to detect daemon starts, may I suggest trepanning22:00
naccLocutusOfBorg: hrm, strange! care to upload?22:05
coreycbslangasek, that was a lame attempt at a fix.. it turned out the service is continually restarting on all arch's, and just not getting lucky on armhf and s390x.  what do you mean by trepanning?22:21
coreycbslangasek, I have a config option change that I'm testing to fix it22:21
slangasekcoreycb: I mean someone needs to let the evil spirits out of the head of whoever thought of implementing the service this way ;)22:21
coreycbslangasek, agreed, it's not very intelligent22:21
naccfrom a process perspective, -updates and -security packages may not go through -proposed? Is that accurate?22:38
naccand by may, I mean 'might'22:38
slangaseknacc: true22:40
naccslangasek: thanks!22:41
Unit193slangasek: FWIW, you can change the topic with  /cs topic #ubuntu-devel Foo  now, when you're identified.22:42
slangasekUnit193: what's '/cs'?22:42
Unit193slangasek: Sorry, /msg ChanServ22:42
slangasekok22:43
naccrbasak: fyi, just shot you a couple MRs, no need to review them, they are for our process discussion22:51
naccsmb: not sure if you've seen LP: #1591695, but given that someone is trying to contribute, would be good to pick up their change, if reasonable23:25
ubottuLaunchpad bug 1591695 in libvirt (Ubuntu) "libvirt-guest.sh will never sucessfully shutdown more than one virtual machine in my setup" [Medium,Triaged] https://launchpad.net/bugs/159169523:25
rbasaknacc: ack, thanks23:27
naccrbasak: also, i'm thinking we might be able to take LP: #1519120 off of the server-next list, unless you think wes should look at the NM changes GUI changes?23:29
ubottuLaunchpad bug 1519120 in network-manager (Ubuntu) "NetworkManager should provide default name for VLAN" [Low,Confirmed] https://launchpad.net/bugs/151912023:29
naccand maybe replace it on the list with LP: #154167823:29
ubottuLaunchpad bug 1541678 in vlan (Ubuntu) "if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names" [High,Confirmed] https://launchpad.net/bugs/154167823:29
naccah i see it was23:30
naccand assigned to you, rbasak :)23:30
rbasaknacc: 120 I disambiguated in #1423:31
rbasakcomment #1423:31
rbasakI'd be fine pulling that from server-next23:31
rbasakAnd only leave us subscribed to follow any non-NM developments23:31
rbasak(since it was confused with the separate vlan package bug)23:31
naccack23:32
nacc(and done)23:32
rbasakThanks!23:32

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