[09:21] <pitti> LocutusOfBorg: thanks! Uploaded
[09:38] -queuebot:#ubuntu-release- New: rejected snapd-glib [source] (xenial-proposed) [1.2-0ubuntu2~xenial2]
[10:26] -queuebot:#ubuntu-release- New binary: libproxy [i386] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:26] -queuebot:#ubuntu-release- New binary: libproxy [ppc64el] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:27] -queuebot:#ubuntu-release- New binary: libproxy [amd64] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:28] -queuebot:#ubuntu-release- New binary: libproxy [arm64] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:29] -queuebot:#ubuntu-release- New binary: libproxy [armhf] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:29] -queuebot:#ubuntu-release- New binary: libproxy [powerpc] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:29] -queuebot:#ubuntu-release- New binary: libproxy [s390x] (zesty-proposed/main) [0.4.13-1] (desktop-core, ubuntu-server)
[10:39] -queuebot:#ubuntu-release- New sync: haskell-mono-traversable-instances (zesty-proposed/primary) [0.1.0.0-2]
[10:41] -queuebot:#ubuntu-release- New sync: rss2irc (zesty-proposed/primary) [1.1-1]
[10:50] <LocutusOfBorg> does anybody care about this testsuite failure? somewhere the sbuild armhf default configuration seems wrong
[10:50] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/haskell-http-conduit/2.1.11-3/+build/11197490
[10:50] <LocutusOfBorg> I can't reproduce on local pbuilder
[10:56] <LocutusOfBorg> in the meanwhile I'll disable it
[11:31] -queuebot:#ubuntu-release- New: accepted fonts-ocr-b [amd64] (zesty-proposed) [0.2~dfsg1-4]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [amd64] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [armhf] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [powerpc] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [s390x] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [sync] (zesty-proposed) [0.1.0.0-2]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [i386] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted rss2irc [sync] (zesty-proposed) [1.1-1]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [arm64] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted libproxy [ppc64el] (zesty-proposed) [0.4.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted gobgp [amd64] (zesty-proposed) [1.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted gobgp [armhf] (zesty-proposed) [1.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted gobgp [ppc64el] (zesty-proposed) [1.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted gobgp [arm64] (zesty-proposed) [1.13-1]
[11:31] -queuebot:#ubuntu-release- New: accepted gobgp [i386] (zesty-proposed) [1.13-1]
[11:34] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [ppc64el] (zesty-proposed/none) [0.1.0.0-2] (no packageset)
[11:34] -queuebot:#ubuntu-release- New binary: rss2irc [ppc64el] (zesty-proposed/none) [1.1-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [i386] (zesty-proposed/none) [0.1.0.0-2] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: rss2irc [i386] (zesty-proposed/none) [1.1-1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [arm64] (zesty-proposed/universe) [0.1.0.0-2] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: rss2irc [amd64] (zesty-proposed/universe) [1.1-1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [amd64] (zesty-proposed/universe) [0.1.0.0-2] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: rss2irc [armhf] (zesty-proposed/universe) [1.1-1] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [armhf] (zesty-proposed/universe) [0.1.0.0-2] (no packageset)
[11:39] -queuebot:#ubuntu-release- New binary: rss2irc [arm64] (zesty-proposed/universe) [1.1-1] (no packageset)
[11:39] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [powerpc] (zesty-proposed/universe) [0.1.0.0-2] (no packageset)
[11:39] -queuebot:#ubuntu-release- New binary: rss2irc [powerpc] (zesty-proposed/universe) [1.1-1] (no packageset)
[11:40] -queuebot:#ubuntu-release- New binary: haskell-mono-traversable-instances [s390x] (zesty-proposed/universe) [0.1.0.0-2] (no packageset)
[11:41] -queuebot:#ubuntu-release- New binary: rss2irc [s390x] (zesty-proposed/universe) [1.1-1] (no packageset)
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [amd64] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [armhf] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [powerpc] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [s390x] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [arm64] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [ppc64el] (zesty-proposed) [1.1-1]
[12:08] -queuebot:#ubuntu-release- New: accepted rss2irc [i386] (zesty-proposed) [1.1-1]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [amd64] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [armhf] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [powerpc] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [s390x] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [arm64] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [ppc64el] (zesty-proposed) [0.1.0.0-2]
[12:09] -queuebot:#ubuntu-release- New: accepted haskell-mono-traversable-instances [i386] (zesty-proposed) [0.1.0.0-2]
[12:13] -queuebot:#ubuntu-release- New binary: util-linux [s390x] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:14] -queuebot:#ubuntu-release- New binary: util-linux [i386] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:14] -queuebot:#ubuntu-release- New binary: util-linux [ppc64el] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:17] -queuebot:#ubuntu-release- New binary: util-linux [amd64] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:17] -queuebot:#ubuntu-release- New binary: util-linux [powerpc] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:17] -queuebot:#ubuntu-release- New binary: util-linux [arm64] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:17] -queuebot:#ubuntu-release- New binary: util-linux [armhf] (zesty-proposed/main) [2.29-1ubuntu1] (core)
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [amd64] (zesty-proposed) [2.29-1ubuntu1]
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [armhf] (zesty-proposed) [2.29-1ubuntu1]
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [powerpc] (zesty-proposed) [2.29-1ubuntu1]
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [s390x] (zesty-proposed) [2.29-1ubuntu1]
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [arm64] (zesty-proposed) [2.29-1ubuntu1]
[12:22] -queuebot:#ubuntu-release- New: accepted util-linux [ppc64el] (zesty-proposed) [2.29-1ubuntu1]
[12:23] -queuebot:#ubuntu-release- New: accepted util-linux [i386] (zesty-proposed) [2.29-1ubuntu1]
[13:10] <cjwatson> LocutusOfBorg: please stop blaming sbuild for random stuff when there's absolutely no evidence that it has anything to do with it.  there'll be a bunch of other environmental differences between the armhf-on-arm64 builders and whatever your pbuilder is running on, and you'd do better to work out which test is failing and to try to see how to get more information out of it than to randomly ...
[13:10] <cjwatson> ... blame sbuild.
[13:12] <LocutusOfBorg> cjwatson, of course I mean sbuild but I mean buildd configuration or whatever, indeed
[13:13] <LocutusOfBorg> the problem is that I don't know how to actually check that, because in my system it is not failing
[13:13] <LocutusOfBorg> and last time I tried to upload in a ppa, armhf was good
[13:13] <cjwatson> LocutusOfBorg: So maybe it's a non-deterministic failure?
[13:14] <LocutusOfBorg> I retried a lot of times when I did the yakkety transition
[13:14] <LocutusOfBorg> deterministic
[13:14] <cjwatson> LocutusOfBorg: PPAs build in exactly the same environment.
[13:14] <cjwatson> LocutusOfBorg: So I don't believe that it won't be reproducible there.
[13:14] <LocutusOfBorg> I just uploaded it
[13:15] <cjwatson> I get that it's frustrating when it's hard to reproduce something, but just saying "hey guys I think this is an infrastructure problem" gets us nowhere.  It's always necessary to make some effort to get more information first.
[13:16] <cjwatson> And we don't have any special access to debug these systems in the way I think you imagine we have
[13:17] <LocutusOfBorg> so, no way in case of failures to see a debug build somewhere, right?
[13:17] <cjwatson> Getting the package build itself to produce more informative output really is the best way to do it
[13:17] <LocutusOfBorg> sure, but I'm pretty sure I remember that it wasn't reproducible in a ppa
[13:18] <LocutusOfBorg> maybe back to xenial's day
[13:18] <LocutusOfBorg> let me check
[13:18] <cjwatson> armhf PPAs used to be quite different
[13:18] <cjwatson> They aren't now
[13:18] <LocutusOfBorg> since when?
[13:19] <LocutusOfBorg> "11 Aug 2016" when I did that checks
[13:20] <cjwatson> It's been changing over the course of this year
[13:20] <cjwatson> Please try again
[13:20] <LocutusOfBorg> build is ongoing
[13:20] <cjwatson> I'd suggest hacking the package build to run the test multiple times
[13:20] <cjwatson> (in a PPA)
[13:21] <pitti> LocutusOfBorg: fixed pkg-create-dbgsym is in zesty now, so you can retry
[13:21] <cjwatson> If there's any possibility that it might have any nondeterminism (and since you don't know what the bug is, you can't tell me that there isn't such a possibility), then you might well end up getting confused by a fluke pass
[13:22] <cjwatson> Basically, do more science
[13:22] <LocutusOfBorg> pitti, I'm waiting for the new lazarus upload in Debian, thanks
[13:22] <LocutusOfBorg> cjwatson, I'll try to debug it further
[13:22] <LocutusOfBorg> thanks
[13:44] -queuebot:#ubuntu-release- Unapproved: cinder (trusty-proposed/main) [1:2014.1.5-0ubuntu2 => 1:2014.1.5-0ubuntu2.1] (ubuntu-server)
[14:50] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (xenial-proposed/universe) [1.3.0-0ubuntu2 => 1.3.0-0ubuntu2.16.04.1] (no packageset)
[14:50] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (yakkety-proposed/universe) [1.3.0-0ubuntu2 => 1.3.0-0ubuntu2.16.10.1] (no packageset)
[15:48] <LocutusOfBorg> sigh, cmake-extras migrated to -release :/ and cmake didn't
[15:48] <LocutusOfBorg> this breaks silo
[15:51] <LocutusOfBorg> pitti, can you kick it out? I have to think how enforce that cmake version to be installed, to avoid them migrating in different timings
[15:52] <LocutusOfBorg> and libuv1 needs a MIR, until that MIR is accepted, cmake-extras reverse-dependencies will be broken
[16:10] <pitti> LocutusOfBorg: right, cmake-extras should grow some versioned dependency on cmake (generated at build time)
[16:11] <LocutusOfBorg> yes but I don't know how
[16:11] <LocutusOfBorg> I didn't find a way like we do when transitioning stuff
[16:11] <LocutusOfBorg> I would appreciate the new cmake not migrating until extras gets a rebuild
[16:11] <LocutusOfBorg> on an unrelated note: cjwatson https://launchpadlibrarian.net/293405094/buildlog_ubuntu-zesty-armhf.haskell-http-conduit_2.1.11-3~build3_BUILDING.txt.gz
[16:12] <LocutusOfBorg> I added the cat of such build log, and the content is the url of the build log itself
[16:12] <LocutusOfBorg> **** DUMPING LOG ****
[16:12] <LocutusOfBorg> Test suite test: RUNNING...
[16:12] <LocutusOfBorg> Test suite test: FAIL
[16:12] <LocutusOfBorg> Test suite logged to: dist-ghc/test/http-conduit-2.1.11-test.log
[16:12] <LocutusOfBorg> **** END LOG ****
[16:12] <pitti> LocutusOfBorg: something like cmake-extras Depends: cmake (>= ${cmake:Version}), cmake (<< ${cmake:nextMajor}) and compute these in debian/rules
[16:13] <LocutusOfBorg> pitti, build-depends or runtime?
[16:13] <pitti> LocutusOfBorg: runtime
[16:13] <LocutusOfBorg> :/
[16:13] <pitti> because that's where it matters
[16:13] <LocutusOfBorg> isn't this some sort of circular dependency stuff?
[16:13] <LocutusOfBorg> probably not, but seems... strange
[16:14] <pitti> no, why would it be?
[16:14] <pitti> cmake doesn't depend on cmake-extras
[16:14] <LocutusOfBorg> probably not, I agree
[16:14] <LocutusOfBorg> Depends: ${misc:Depends}, cmake (>= 3.7~), cmake (<< 3.8)
[16:15] <LocutusOfBorg> this might be good and stupid enough
[16:15] <pitti> right, except that the 3.7 and 3.8 should be computed dynamically via substvars
[16:15] <LocutusOfBorg> I'm not good at writing that code :/
[16:15] <pitti> but that should result in a dependencies like the above indeed
[16:15] <LocutusOfBorg> I'll try
[16:16] <cjwatson> LocutusOfBorg: I don't remember how to get more information out of Haskell test suites
[16:17] <cjwatson> Hopefully there's some kind of verbose option somewhere
[16:19] <LocutusOfBorg> I remember doko asking that option many times with no answer
[16:19] <pitti> LocutusOfBorg: something like CMAKE_VERSION=$(shell dpkg -s cmake | sed -n '/^Version/ {s/^.*: *//; p}' | cut -f1,2 -d.)
[16:19] <pitti> LocutusOfBorg: and then using that as a lower bound, and $(CMAKE_VERSION)z as a high bound? so that you get (<< 3.7z)?
[16:20] <cjwatson> LocutusOfBorg: You could ask the specific upstream for this package, perhaps.
[16:21] <LocutusOfBorg> I prefer dpkg-query
[16:21] <LocutusOfBorg> but it seems to be not working $$(dpkg-query --show --showformat='$${version}' cmake)
[16:22] <pitti> # dpkg-query -f'${Version}' --show cmake | cut -f1,2 -d.
[16:22] <pitti> 3.6
[16:22] <pitti> LocutusOfBorg: ^
[16:22] <pitti> no double $
[16:22] <pitti> ' ' already escapes
[16:23] -queuebot:#ubuntu-release- New: rejected python-vmware-nsxlib [source] (zesty-proposed) [0.2.0-0ubuntu1]
[16:23] <LocutusOfBorg> indeed, I'm still not confident with that, but I'll try to make a good upload
[16:23] <LocutusOfBorg> I don't like because cmake might start doing some bad versioning, and cut will fail
[16:23] <LocutusOfBorg> I'm always not confident with such "cut", I would appreciate way more dpkg-query to return the upstream version
[16:27] <cjwatson> I'm not quite sure why ${source:Upstream-Version} doesn't work; it would match deb-substvars(5) if it did
[16:28] <cjwatson> worth a dpkg bug perhaps
[16:31] <LocutusOfBorg> cjwatson, --> https://github.com/yesodweb/yesodweb.com-content/issues/181
[16:31] <LocutusOfBorg> followed your advice
[16:33] <LocutusOfBorg> cjwatson, I think I'll open a bug
[16:38] <bdmurray> infinity, slangasek: Is there a 16.04.2 release date?
[16:43] <LocutusOfBorg> pitti, can I upload? unfortunately -release will be broken, and -proposed fixed until cmake migrates
[16:43] <pitti> LocutusOfBorg: upload the tighter dependency? sure, please do
[16:45] <LocutusOfBorg> so, the versioning should be:
[16:45] <LocutusOfBorg> 3.7 < 3.7.1 < 3.7.9z < 3.8
[16:46] <LocutusOfBorg> 3.7 < 3.7.1 < 3.7z < 3.8
[16:46] <LocutusOfBorg> this is better ^^
[16:46] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/cmake-extras/0.7+16.04.20160513-0ubuntu4
[16:50] <pitti> LocutusOfBorg: I'd drop the microversion from it, as cmake-extras only ships stuff in MAJOR.MINOR/ dirs
[16:50] <pitti> there is no reason to break it on microversion updates, as a rebuild will look exactly the same
[16:51] <pitti> LocutusOfBorg: oh, on second look I figure that's actually what you meant
[16:51] <LocutusOfBorg> :)
[16:52] <LocutusOfBorg> for people interested: https://bugs.debian.org/844348
[16:52] <ubot5`> Debian bug 844348 in src:dpkg "dpkg: please support ${source:Upstream-Version} in query" [Normal,Open]
[16:55] <LocutusOfBorg> haskell transition is mostly finished, needs autopkgtestsuite runs against proposed, a ghc build I uploaded some seconds ago, and some removals that are affecting debian too
[16:56] <LocutusOfBorg> ppc64el stuff should be fixed with this new ghc
[16:59] <LocutusOfBorg> pitti, last question for today, I mostly promise
[16:59] <LocutusOfBorg> why some testsuite is shown as running, but the queue has no that package?
[16:59] <LocutusOfBorg> autopkgtest for haskell-hoogle/5.0.1+dfsg1-1: amd64: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
[16:59] <LocutusOfBorg> I see lots of "in progress" that fails to complete because they seems to be not run
[17:08] <pitti> LocutusOfBorg: there were some cases where tests exited with code 12 because the source packages failed to unpack; britney doesn't see those results
[17:08] <pitti> LocutusOfBorg: I'll be back in ~ 3 hours, will look at that then
[17:10] <LocutusOfBorg> thanks
[17:26] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-3ubuntu1 => 2.02~beta3-3ubuntu1] (core)
[17:26] -queuebot:#ubuntu-release- Unapproved: python-glanceclient (trusty-proposed/main) [1:0.12.0-0ubuntu1 => 1:0.12.0-0ubuntu1.1] (ubuntu-server)
[17:29] <slangasek> bdmurray: if it's not on the schedule yet, I don't have one.  infinity what's the process for picking/setting the point release dates?
[17:31] -queuebot:#ubuntu-release- Unapproved: cups (xenial-proposed/main) [2.1.3-4 => 2.1.3-4ubuntu0.1] (core)
[17:45] <slangasek> pitti, Laney: looks to me from http://autopkgtest.ubuntu.com/running that some test requests have gone missing again (e.g.: lammps, amd64/i386/ppc64el; valgrind, amd64/i386/ppc64el).  I don't feel I have a handle on where these requests have gone when they disappeared; short of just cronning a mass-retry, how do we debug this?
[17:47] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-3ubuntu1 => 2.02~beta3-3ubuntu1] (core)
[18:03] <sergiusens> slangasek hey, mind letting snapcraft into xenial-updates and yakkety-updates?
[18:03] <slangasek> sergiusens: looking
[18:14] <sergiusens> thanks
[18:14] <slangasek> sergiusens: done
[18:51] <Laney> slangasek: LocutusOfBorg just asked that and pitti said he'd debug later on - I don't have a good feel for where to start looking ATM
[18:51] <slangasek> ok
[18:52] <Laney> pitti: or you can walk me through this with you tomorrow morning if you want
[18:52] <Laney> I mean I could start groping around but it might not be the most efficient way to do it
[18:55] <Laney> although...
[18:56] <Laney> there's a lot of
[18:56] <Laney> Nov 11 15:10:54 juju-prod-ues-proposed-migration-machine-3 sh[7686]: requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)
[18:56] <Laney> Nov 11 15:10:54 juju-prod-ues-proposed-migration-machine-3 sh[7686]: During handling of the above exception, another exception occurred:
[18:56] <Laney> in the log
[18:58] <Laney> also Nov 13 20:46:26 juju-prod-ues-proposed-migration-machine-3 sh[6824]: 2016-11-13 20:46:26,801 [6824] INFO: autopkgtest exited with code 20
[18:59] <Laney>        20   other unexpected failures including bad usage
[18:59] <Laney> ._.
[19:01] <Laney> ^- 6824 was valgrind/ppc64el
[19:06] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/v/valgrind/20161113_204627_265a1@/log.gz
[19:07] <Laney> that was supposed to be fixed by 3bee404
[19:43] -queuebot:#ubuntu-release- New sync: linux-hwe-edge (xenial-proposed/primary) [4.8.0-27.29~16.04.1]
[19:46] -queuebot:#ubuntu-release- New: accepted linux-hwe-edge [sync] (xenial-proposed) [4.8.0-27.29~16.04.1]
[19:58] -queuebot:#ubuntu-release- Unapproved: ghostscript (yakkety-proposed/main) [9.19~dfsg+1-0ubuntu6 => 9.19~dfsg+1-0ubuntu6.1] (desktop-core, ubuntu-server)
[20:10] <pitti> Laney: so indeed haskell-google ran a ton of times after Nov 02 (last date on http://autopkgtest.ubuntu.com/packages/h/haskell-hoogle/zesty/amd64)
[20:10] <pitti> Laney: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty?format=plain&prefix=zesty/amd64/h/haskell-hoogle
[20:11] <pitti> Laney: this is explained in https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Container_Layout and the following paragraph
[20:11] <pitti> hm, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/h/haskell-hoogle/20161114_120110_e5db9@/log.gz
[20:11] <pitti> \: command not found
[20:11] <pitti> that again
[20:11] <pitti> I already fixed two instances of that
[20:12] <Laney> pitti: hm?
[20:12] <slangasek> you fixed it so that the \ command is found?
[20:12] <pitti> ₥e goes to chase trailing spaces
[20:12] <pitti> err, what on earth is that?
[20:12] <slangasek> hah
[20:12] <slangasek> ₥
[20:12] <pitti> wow, that's compose-/me
[20:13] <pitti> /usr/bin/\ :)
[20:13] <pitti> nah, curious effect of bash 4.4 (new in zesty) plus the wonderfully nested quoting of two shell scripts through ssh
[20:13] <pitti> the first instance took me over an hour, the second 3 mins, let's see how long that will be
[20:14] <slangasek> øµɨđħŧ⌿ƀ₥ √ƶǥ¢ what a strange set of compose options
[20:14]  * Laney only sees one in git
[20:15] <pitti> Laney: the other is in autopkgtest-cloud
[20:15] <pitti> slangasek: is that compose-/-<any letter> ?
[20:15] <slangasek> pitti: yeah basically
[20:18] <Laney> pitti: oh right, I can see it then
[20:18] <pitti> ${REL}-proposed; " ← space
[20:18] <pitti> I'll reproduce it locally and then fix it (should be simple)
[20:19] <Laney> yes
[20:26] <pitti> Laney: I found the command, but a more generic solution will be more robust: testing https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=812d04661 now (it does work with the above haskell-hoogle)
[20:38] <pitti> ok, LGTM, mass-retrying now
[20:40] <pitti> or rather, retrying http://autopkgtest.ubuntu.com/running#pkg-r-cran-shiny for now, if that works end-to-end, retrying the rest
[20:42] <pitti> muuuch better
[20:45] <Laney> pitti: nice
[20:45] <Laney> BTW I already understood the container layout - that's how I found the valgrind link that I gave just above your text
[20:46] <pitti> ah, good
[20:46]  * pitti pushes retry-autopkgtest-regressions --help change that runs 10 wgets in parallel
[20:46] <Laney> exit 20 causing things to remain as in progress but not actually be running is not very good
[20:46] <pitti> xargs, you are amazing
[20:47] <pitti> Laney: indeed, right now britney ignores results without a testpkg-version artifact as it cannot assign them to anything
[20:47] <pitti> Laney: and testpkg-version does not exist because it failed before being able to download the source package to determine that
[20:47] <pitti> so, a bit tricky
[20:48] <pitti> that's a new/rare kind of problem, we haven't had that in a loong time
[20:48] <pitti> (tests going missing en masse; the previous one was bug 1571353)
[20:48] <ubot5`> bug 1571353 in Auto Package Testing "test results get lost and stay "in progress" forever when multiple tests finish at the exact same time" [Medium,Fix released] https://launchpad.net/bugs/1571353
[20:52] <Laney> pitti: oh right, so could we put the version in as part of the request?
[20:52] <Laney> autopkgtest ... package/version
[20:52] <pitti> Laney: we can't predict the version accurately
[20:52] <Laney> britney knows it
[20:52] <pitti> well, it could know, but not righ tnow
[20:53] <pitti> i. e. it could check whether the released or the proposed version of the tested package is going to be tested (via analysis of transitive Depends: of the trigger)
[20:53] <pitti> but it's not really easy
[20:54] <pitti> Laney: what would be better is to generate a random hash, add it as an env variable, and read it back from the artifacts, and keep it in pending.json
[20:54] <pitti> then you can match completely failed results too
[20:54] <pitti> (still not sure if it's worth the trouble -- it won't significantly reduce the time for analyzing the real bug)
[20:55] <pitti> we already do the env/read back exercise for the "trigger"
[20:58] <Laney> pitti: Well this time you didn't hear about the bug for a long time because nobody checked tests that britney was claiming were in progress
[20:59] <Laney> Until they got suspicious
[20:59] <pitti> right, and today I didn't check excuses.html yet
[21:05] <Laney> pitti: Could you just make up a testpkg-version?
[21:09]  * Laney goes away
[21:10] -queuebot:#ubuntu-release- Unapproved: cups-filters (yakkety-proposed/main) [1.11.4-0ubuntu2 => 1.11.4-0ubuntu2.1] (desktop-core, ubuntu-server)
[21:14] <pitti> Laney: hmm, we could -- just "testpkg" or "testpkg-none" or so, not sure if that would confuse other consumers
[21:15] <pitti> Laney: but this would then also hit random apt failures, connection/DNS/hash sum errors, and what not -- in many of these cases you want an auto-retry instead of declaring it a test failure (as there's nothing wrong with the test)
[21:16] <pitti> so in the beginning we had a lot of displayed failures due to random testbed/network issues
[21:16] <pitti> now the pendulum is more in favor of "tmpfail"/auto-retry
[21:22] <tkamppeter> Can you please reject cups-filters 1.11.4-0ubuntu2.1, I have forgotten to add the bug number (bug 1637583) to it.
[21:22] <ubot5`> bug 1637583 in ghostscript (Ubuntu Yakkety) "PWG Raster printing on IPP Everywhere printers not working correctly" [High,In progress] https://launchpad.net/bugs/1637583
[21:22] <pitti> tkamppeter: done
[21:23] -queuebot:#ubuntu-release- Unapproved: rejected cups-filters [source] (yakkety-proposed) [1.11.4-0ubuntu2.1]
[21:29] -queuebot:#ubuntu-release- Unapproved: cups-filters (yakkety-proposed/main) [1.11.4-0ubuntu2 => 1.11.4-0ubuntu2.1] (desktop-core, ubuntu-server)
[21:29] <tkamppeter> pitti, thanks. I have replaced the package now.
[22:21] <Laney> pitti: Those are tmpfail and requeued, no?
[23:17] -queuebot:#ubuntu-release- New binary: purpose [ppc64el] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: purpose [amd64] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: purpose [s390x] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: purpose [i386] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:20]  * tsimonq2 claims responsibility for those new purpose binaries
[23:20] -queuebot:#ubuntu-release- New binary: purpose [arm64] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: purpose [powerpc] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:21] <tsimonq2> If those could get looked at, that would be awesome. :)
[23:23] -queuebot:#ubuntu-release- New binary: libpod-weaver-section-support-perl [amd64] (zesty-proposed/none) [1.007-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: libpod-elemental-transformer-list-perl [amd64] (zesty-proposed/universe) [0.102000-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: purpose [armhf] (zesty-proposed/universe) [1.1-2ubuntu1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: recursive-narrow [amd64] (zesty-proposed/universe) [20140811.1546-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-hard-disk-led [amd64] (zesty-proposed/universe) [13~git20160916.6fe27b2-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: iedit [amd64] (zesty-proposed/universe) [0.9.9.9-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: golang-github-pivotal-golang-clock [amd64] (zesty-proposed/universe) [0.0~git20151018.0.3fd3c19-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: libwww-shorten-github-perl [amd64] (zesty-proposed/universe) [0.1.7-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: libconfig-methodproxy-perl [amd64] (zesty-proposed/universe) [0.02-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: r-cran-rentrez [amd64] (zesty-proposed/universe) [1.0.4-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: ido-ubiquitous [amd64] (zesty-proposed/universe) [3.14-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: node-regenerator-runtime [amd64] (zesty-proposed/universe) [0.9.5-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: node-grunt-contrib-clean [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset)