/srv/irclogs.ubuntu.com/2017/07/29/#ubuntu-release.txt

-queuebot:#ubuntu-release- New binary: mythtv [s390x] (artful-proposed/multiverse) [2:29.0+fixes.20170728.696806310a-0ubuntu1] (mythbuntu)00:01
-queuebot:#ubuntu-release- New binary: mythtv [i386] (artful-proposed/multiverse) [2:29.0+fixes.20170728.696806310a-0ubuntu1] (mythbuntu)00:09
-queuebot:#ubuntu-release- New binary: mythtv [amd64] (artful-proposed/multiverse) [2:29.0+fixes.20170728.696806310a-0ubuntu1] (mythbuntu)00:22
-queuebot:#ubuntu-release- New binary: mythtv [arm64] (artful-proposed/multiverse) [2:29.0+fixes.20170728.696806310a-0ubuntu1] (mythbuntu)02:12
-queuebot:#ubuntu-release- New binary: mythtv [armhf] (artful-proposed/multiverse) [2:29.0+fixes.20170728.696806310a-0ubuntu1] (mythbuntu)02:23
flocculantinfinity: hi - not often I shout out, but we've now been trying to sort out our 'simple' Xubuntu since 16.04.1 https://code.launchpad.net/~xubuntu-dev/livecd-rootfs/xubuntu-base https://code.launchpad.net/~xubuntu-dev/debian-cd/xubuntu-base https://code.launchpad.net/~xubuntu-dev/ubuntu-cdimage/xubuntu-base02:45
flocculantnot sure what we really need to be doing but, we would really like to see this sorted in one way or the other for the next lts02:46
tsimonq2flocculant: Why don't you add something to the official infra (like with Kubuntu's (deprecated) other images and Lubuntu Next, for example)? Just curious.02:47
flocculanttsimonq2: iirc we tried all that 2 years ago - really just want offical answers here now thanks02:49
tsimonq2flocculant: Sure, I just know Adam's a busy guy, wanted to see if I could give you a hand, but if you'd like to wait for him, that's your choice :)02:50
tsimonq2Had a discussion in another channel, forget I said anything here.03:20
flocculantbut you had to comment ...03:27
flocculantsigh03:27
LocutusOfBorgcan you please remove libldap-2.4-2-dbg, slapd-dbg?07:04
infinityLocutusOfBorg: Wrong question.08:21
infinityLocutusOfBorg: Or rather, you wanted to add "in artful-proposed".08:21
infinity(done)08:22
LocutusOfBorgthanks, but the dbg package exists in release, not in proposed... sorry if I wasn't clear, but I don't get it :)09:18
LocutusOfBorgbtw do you have any clue for my notmuch debug logs? with strace and valgrind09:18
infinityLocutusOfBorg: You were asking me to remove them because britney was listing them as "old binaries left..."09:47
infinityLocutusOfBorg: "old binaries left on amd64: libldap-2.4-2-dbg, slapd-dbg (from 2.4.44+dfsg-8ubuntu2)"09:47
infinityLocutusOfBorg: Note the version there.  That's not the version in the release pocket, it was a previous upload that never made it out of proposed.09:47
infinityLocutusOfBorg: (Yes, they exist in the release pocket too, but they SHOULD, until migration happens)09:48
LocutusOfBorgok thanks10:03
-queuebot:#ubuntu-release- New binary: farmhash [amd64] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:09
-queuebot:#ubuntu-release- New binary: farmhash [s390x] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:09
-queuebot:#ubuntu-release- New binary: farmhash [ppc64el] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:09
-queuebot:#ubuntu-release- New binary: farmhash [arm64] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:11
-queuebot:#ubuntu-release- New binary: farmhash [i386] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:11
-queuebot:#ubuntu-release- New binary: farmhash [armhf] (artful-proposed/universe) [0~20170626-g23eecfb-1] (no packageset)11:11
LocutusOfBorginfinity, sorry for  being pesty, but an hint for notmuch will be so much appreciated, I'm really worried about miscompilation of our toolchain on armhf11:25
infinityLocutusOfBorg: Sorry, I haven't really been paying attention.  What have you tried, and what have you managed to discover?  Logs, notes?11:26
LocutusOfBorgI did a run of the test under strace gdb and another with valgrind gdb11:27
LocutusOfBorgI see SIGKILL being started11:27
LocutusOfBorgthis one with valgrind https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/1316623211:27
LocutusOfBorgthe valgrind output is between BEGIN LOG and END LOG11:28
LocutusOfBorghttps://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13161434 this one is with strace11:30
LocutusOfBorg(keyword is BEGIN OUTPUT=11:30
LocutusOfBorg+==15994== Invalid read of size 411:33
LocutusOfBorg+==15994==    at 0x499D362: ??? (in /usr/lib/arm-linux-gnueabihf/libpython3.6m.so.1.0)11:33
LocutusOfBorgthis in particular looks scary to me11:33
-queuebot:#ubuntu-release- New: accepted farmhash [amd64] (artful-proposed) [0~20170626-g23eecfb-1]11:39
-queuebot:#ubuntu-release- New: accepted farmhash [armhf] (artful-proposed) [0~20170626-g23eecfb-1]11:39
-queuebot:#ubuntu-release- New: accepted farmhash [ppc64el] (artful-proposed) [0~20170626-g23eecfb-1]11:39
-queuebot:#ubuntu-release- New: accepted farmhash [arm64] (artful-proposed) [0~20170626-g23eecfb-1]11:39
-queuebot:#ubuntu-release- New: accepted farmhash [s390x] (artful-proposed) [0~20170626-g23eecfb-1]11:39
-queuebot:#ubuntu-release- New: accepted farmhash [i386] (artful-proposed) [0~20170626-g23eecfb-1]11:39
LocutusOfBorginfinity, if you want I did both logs in a single run https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz11:50
infinityLocutusOfBorg: So, this is curious.  I just ran the build (with testsuite) on a machine basically identical to the builders, and it passed.12:05
infinityThe only exception is that I didn't run it under linux32.  I'll try that now.12:05
infinityLocutusOfBorg: Aaaand, went fine under linux32 as well.  So, uhm.  Wat.12:11
infinityI wonder if this is a qemu/kvm bug. :/12:11
infinityLocutusOfBorg: I think it's fair to say that notmuch itself isn't being miscompiled here.  However, that leaves open the question of WTF *is* going wrong with the testsuite on the buildds.12:20
LocutusOfBorgthe question now is: did the qemu/kvm got upgraded in the meanwhile?12:36
LocutusOfBorgthe latest successful build is here  created on 2016-03-13  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/934482612:37
LocutusOfBorgand the first bad is this one:  Started on 2016-08-31  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1060000212:37
LocutusOfBorgKernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon Jan 11 13:24:41 UTC 2016 armv7l12:37
LocutusOfBorgKernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 28 21:24:20 UTC 2016 aarch6412:37
LocutusOfBorgso, in the first case armhf was ran on top of an armv7 kernel, in the other case it became an arm64 one12:38
LocutusOfBorgthis might not even be a regression in qemu/kvm, but rather a change in buildd system that spot a new bug12:38
LocutusOfBorgI'm doing a xenial build here https://launchpad.net/%7Ecostamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+delete-packages12:40
LocutusOfBorgjust to see if this is still building on xenial toolchain12:40
LocutusOfBorgsomething strange is happening on autopkgtest builders14:21
LocutusOfBorgnplan is building since days, being retried continuously (according to the webpage)14:21
LocutusOfBorgTriggers:['python3-defaults/3.6.1-0ubuntu2']14:22
LocutusOfBorgRequester:costamagnagianfranco14:22
LocutusOfBorgthe log seems to be however not showing it14:22
LocutusOfBorgLaney, can you please have a quick look? :)14:23
infinityLocutusOfBorg: The successful build you pointed at wasn't done under qemu.14:28
infinityLocutusOfBorg: kishi was bare metal armv7, bos01* are qemu/kvm instances on armv8 hardware.14:30
infinityLocutusOfBorg: My local test was on hardware nearly identical to bos01*, but not under qemu/kvm.14:30
LocutusOfBorgin fact, I retried a xenial build, and it failed now14:30
infinityLocutusOfBorg: Hence my blaming qemu/kvm, for now.14:30
LocutusOfBorgnow, I tried a xenial build with strace, so I can see if the SIGILL is the same14:30
LocutusOfBorgin case, how to report such qemu/kvm issues?14:31
infinityMight take some more digging to make it a useful bug report.14:31
LocutusOfBorgyep, but I don't know how to easily reproduce, and I don't have access to the infra14:32
infinityBut for now, "fails the testsuite under qemu/kvm, works fine on real hardware" filed against qemu *and* linux (could be kernel or qemu) would be a start.14:32
* infinity goes to get some sleep.14:32
* LocutusOfBorg just woke up :p14:33
LocutusOfBorgthanks infinity I will, and maybe subscribe you for knowledge if you want14:33
LocutusOfBorgsince armhf is fine, can we please have a rebuild of perl stuff against proposed pocket?15:26
LocutusOfBorgcan anybody please remove libjaxp1.3-java-gcj? it seems to be NBS libjaxp1.3-java (1.3.05-2ubuntu3 to 1.3.05-3)17:17
slangasekdoko, apw: looks like binutils 2.29 is blocked for a bit in artful-proposed because linux-tools still has a dep on binutils (< 2.29); what would be the timeline for 4.11.0-12?17:24
slangasekLocutusOfBorg: buh, how does proposed-migration not get that case right?  sorting17:29
LocutusOfBorgI don't know, sorry :) sometimes I'm not sure about what is automagic and what needs hammer17:30
slangasekLocutusOfBorg: yeah, my griping here is that this seems like something we *ought* to have made automagic before now but it clearly isn't17:31
slangasekthis is the "source package previously did arch: any builds, now is arch: all only"17:31
LocutusOfBorgmmm I don't fully get it17:32
LocutusOfBorgok the any-> all move, but two binaries disappeared too17:32
LocutusOfBorg(well, one  because the dbgsym is not a real binary I guess for your system)17:33
slangaseksomething in the code assumes that if there are no arch-specific binaries and it previously saw some, this means the package isn't yet built :P17:33
LocutusOfBorgoh, interesting :)17:34
LocutusOfBorgmeh, as long as you are around, my minions are happy to do more work17:34
apwslangasek, it ought to be copyable out to -proposed on monday17:42
apwslangasek, possibly before if we decide we don't care about the one that is there17:43
slangasekapw: Monday sounds fine to me. how long from copy-to-proposed to ready-to-migrate?17:44
apwnormally testing is a day assuming it is good17:44
* slangasek hits a bunch more perl autopkgtests with a hammer, then goes afk17:48
slangasekapw: yeah, a couple more days is fine, thanks.  I just wanted to understand whether we were looking at 3 weeks of blockage or something, given that the gcc-7 transition is due to start next week17:48
LocutusOfBorgthanks slangasek for perl :D17:49
LocutusOfBorgI did a no-change rebuild of src:stacks because of armhf and s390 were in some "new queue", before they were not built, and after they appeared after the package migrated17:55
LocutusOfBorgfor this reason they ended up in some "limbo" in artful-proposed17:56
LocutusOfBorg stacks | 1.46-1        | artful/universe          | source, amd64, arm64, i386, ppc64el17:56
LocutusOfBorg stacks | 1.46-1        | artful-proposed/universe | armhf, s390x17:56
LocutusOfBorghopefully rebuilding should work17:56
* LocutusOfBorg goes AFK, have a nice saturday to everybody17:56
slangasekLocutusOfBorg: I don't know why you reuploaded samtools.  samtools was already built against libhts2 and was already a candidate for migration; now the libhts transition is delayed further19:05
slangasekLocutusOfBorg: and stacks was also fine, the new binaries simply depended on the newer samtools migrating first because the samtools in artful had no s390x or armhf builds19:07
slangasekLocutusOfBorg: in fact, it looks like you reuploaded all the revdeps of htslib without checking whether this was required19:46
LocutusOfBorgI didn't get the stacks issue, I thought this was a "migrating in different timelines" issue21:31
LocutusOfBorgI saw that all of them were already built, and I even looked at build logs, but I thouth britney wasn't able to let them migrate because of same versions already in archive or something similar21:32
LocutusOfBorgI remember in the past some race-condition caused similar issues, and no-change rebuilding was the fix21:32
LocutusOfBorgsorry!21:32
slangasekLocutusOfBorg: did you look at update_output.txt?22:02
slangasekit should have shown that all of these packages were ready to migrate and that only blasr was holding up - they literally would've migrated in the next p-m run :)22:03
slangasekanyway, they've migrated now, with a bit of skiptesting of the redundant test runs22:03
LocutusOfBorgyes, I looked at it, and I saw samtools on s390x22:08
LocutusOfBorgI looked at runtime dependencies of samtools, to see if some perl was holding it22:08
LocutusOfBorgand I found nothing, literally nothing22:08
LocutusOfBorgand then I though about a race condition, nice to see it fixed :)22:09
LocutusOfBorgprobably britney was showing s390x because it is the first architecture tested?22:09
LocutusOfBorgstarting by amd64 would be better, at least "testable" in my pbuilder environment22:10
LocutusOfBorgand auto-trackers will save me for badly understanding britney!22:14
LocutusOfBorganyway, g'night!22:14
LocutusOfBorgdoko, lots of qt stuff will fail with gcc-7, so I presume I will upload 5.9 after gcc-7 switch, to avoid useless bug fixing22:15
LocutusOfBorgqt is already mostly ready-to-land in silo22:16
LocutusOfBorgtsimonq2, ^^22:16
tsimonq2Works for me.22:17

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