[00:12] -queuebot:#ubuntu-release- Unapproved: snapd-glib (bionic-proposed/main) [1.39-0ubuntu1 => 1.40-0ubuntu0.18.04.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[00:12] -queuebot:#ubuntu-release- Unapproved: snapd-glib (bionic-proposed/main) [1.39-0ubuntu1 => 1.41-0ubuntu0.18.04.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[06:35] <ginggs> would someone please 'force-badtest pyfai/0.15.0+dfsg1-1/amd64' ?  It passed once by accident on 2018-06-01  http://autopkgtest.ubuntu.com/packages/p/pyfai/cosmic/amd64
[07:25] <RAOF> Bah! Why is gst-plugins-bad1.0 not migrating to cosmic?
[07:26] <RAOF> It, and all of it's dependencies, appear to be valid candidates in update_excuses.
[07:29] <apw> RAOF, your answer will be in update_output.txt
[07:29] <RAOF> And update_output is rather inscrutable.
[07:31] <RAOF> Is the skipped…. s390x:  <big long list of packages> the list of packages that an update would make uninstallable?
[07:33] <apw> RAOF, yeah so migrating all the valid things would make that mess (only one arch is reported iirc and not always the same one)
[07:33] <apw> RAOF, pming you some bits
[08:03] <Laney> It ends up being entangled in other transitions
[08:36] -queuebot:#ubuntu-release- Unapproved: dovecot (bionic-proposed/main) [1:2.2.33.2-1ubuntu4 => 1:2.2.33.2-1ubuntu4.1] (ubuntu-server)
[10:23] -queuebot:#ubuntu-release- Unapproved: rfkill (xenial-proposed/main) [0.5-1ubuntu3 => 0.5-1ubuntu3.1] (desktop-core)
[10:28] <LocutusOfBorg> bdmurray, ^^ thanks for the reject :)
[11:31] -queuebot:#ubuntu-release- Unapproved: accepted openipmi [source] (bionic-proposed) [2.0.22-1.1ubuntu2.1]
[11:31] -queuebot:#ubuntu-release- Unapproved: accepted openipmi [source] (artful-proposed) [2.0.22-1.1ubuntu1.1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted openipmi [source] (xenial-proposed) [2.0.18-0ubuntu11.2]
[11:41] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (artful-proposed) [3.186.3]
[11:41] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.1]
[11:42] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.9]
[11:49] <doko> RAOF: it usually helps if you can fix blocking issues
[11:51] -queuebot:#ubuntu-release- Unapproved: accepted rfkill [source] (xenial-proposed) [0.5-1ubuntu3.1]
[11:58] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (artful-proposed) [1:17.10.15]
[12:06] -queuebot:#ubuntu-release- Unapproved: accepted boinc [source] (bionic-proposed) [7.9.3+dfsg-5ubuntu2]
[13:45] <sil2100> rbasak: would you mind if I review initramfs-tools for xenial/artful now?
[13:46] <sil2100> rbasak: I was supposed to review it yesterday but it had some issues that only got fixed after my EOD
[13:49] -queuebot:#ubuntu-release- New: accepted openstack-trove [amd64] (cosmic-proposed) [1:10.0.0~b1-0ubuntu1]
[13:49] -queuebot:#ubuntu-release- New: accepted zaqar [amd64] (cosmic-proposed) [7.0.0~b1-0ubuntu1]
[13:49] -queuebot:#ubuntu-release- New: accepted sahara [amd64] (cosmic-proposed) [1:9.0.0~b2-0ubuntu1]
[13:58] <rbasak> sil2100: sure - I'm done processing SRUs for today.
[14:20] -queuebot:#ubuntu-release- New binary: networking-sfc [amd64] (cosmic-proposed/universe) [7.0.0~b2-0ubuntu2] (no packageset)
[14:32] -queuebot:#ubuntu-release- New binary: networking-ovn [amd64] (cosmic-proposed/universe) [5.0.0~b2-0ubuntu2] (no packageset)
[15:11] <juliank> Laney, sil2100 https://trello.com/c/RAnrwNw1/17-make-the-retry-button-reuse-the-same-triggers-as-the-last-run
[15:12] <juliank> does this make sense, smarter retry button for autopkgtest?
[15:12] <sil2100> juliank: I would say yes, since I actually would expect it to work like that
[15:14] <Laney> what makes the last set of triggers the right set and not someone randomly playing around (e.g. adding all-proposed)?
[15:17] <Laney> Like, if you added a trigger and there's a retry button still, sounds like that means the run failed and the trigger wasn't right/enough anyway
[15:24] <doko> Laney: how would you determine the minimal set of triggers? e.g. for vtk7, triggered by openmpi?
[15:24] <Laney> doko: not sure what that has to do with what the retry button does?
[15:25] <Laney> (Note that you can retry with a previous run's set of triggers from autopkgtest.u.c already)
[15:25] <doko> I'm not aware of that. how would I do that?
[15:26] <Laney> http://autopkgtest.ubuntu.com/packages/python-pydap/cosmic/armhf
[15:26] <Laney> See the links there for example
[15:27] <doko> hmm, so how did ginggs find out about these triggers?
[15:27] <Laney> I don't know, some domain specific knowledge?
[15:28] <Laney> This seems orthogonal to the original question to me
[15:28] <doko> right, domain specific knowledge for any random package
[15:29] <Laney> It would have been better for the maintainer to have specified that a newer numpy was required there.
[15:29]  * ginggs searched for update_excuses for python-pydap looking for other packages that it needed to be tested against
[15:30] <doko> Laney: the original thing is that with every new openmpi upload, the tests triggered by openmpi are failing again. and how best to fix that
[15:30] <Laney> The original thing to me was a question about uthe retry button.
[15:31] <doko> yes, because I usually retrigger the openmpi tests with all-proposed=1
[15:31] <Laney> If new openmpi uploads break previously built things, it sounds like that should be expxressed in the package somehow.
[15:31] <doko> so add a delta just for the autopkg tests and hope that nobody discards that with the next sync?
[15:32] <Laney> I said 0 of the things you just asserted.
[15:32] <doko> "should be expxressed in the package somehow"
[15:33] <doko> but maybe I'm not reading between the lines
[15:33] <Laney> It almost certainly should *not* be a delta, for one.
[15:33] <Laney> And it's not clear that this would be "just" for the tests.
[15:34] <Laney> If it's possible to install a broken set of packages, that'd probably apply to non-test usecases too.
[15:34] <doko> so you mean to express this by a hint?
[15:34] <Laney> No, more like a versioned package relationship.
[15:34] <ginggs> a new upload of openmpi upload doesn't break things, britney runs the tests against the versions of the packages in testing instead of in proposed - all of the tests need to triggered again
[15:35] <Laney> ginggs: What is wrong about the versions in testing that they fail?
[15:35] <ginggs> Laney: they are compiled against openmpi2 not openmpi3
[15:36] <ginggs> this discussion should probably go to #debci
[15:36] <ginggs> britney needs to learn there's a transition going on and trigger the right group of packages together
[15:39] <Laney> Sorry, we went on an extreme tangent from a simple question about the generated retry button and I don't really have time to get into this in depth.
[15:39] <ginggs> regarding the retry button, I think it would be really useful if successful tests also had a retry button, so I could copy the link and make a minor change
[15:42] <ginggs> ...on this page http://autopkgtest.ubuntu.com/packages/python-pydap/cosmic/armhf not update_excuses
[15:47] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (artful-proposed) [0.125ubuntu12.2]
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.12]
[16:05] -queuebot:#ubuntu-release- New: accepted networking-ovn [amd64] (cosmic-proposed) [5.0.0~b2-0ubuntu2]
[16:05] -queuebot:#ubuntu-release- New: accepted networking-sfc [amd64] (cosmic-proposed) [7.0.0~b2-0ubuntu2]
[16:29] -queuebot:#ubuntu-release- New binary: senlin [amd64] (cosmic-proposed/universe) [6.0.0~b2-0ubuntu1] (no packageset)
[17:04] <mitya57> Can someone please mark three autopkgtests that block sphinx migration as ignored failures? pyfai/amd64, python-asdf/armhf and xonsh (all archs)
[17:04] <mitya57> I have verified that they have nothing to do with sphinx, and not trivial to fix
[17:13] -queuebot:#ubuntu-release- New binary: puppet-module-arioch-redis [amd64] (cosmic-proposed/none) [3.2.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: c-sig [amd64] (cosmic-proposed/universe) [3.8-22] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: ruby-turbolinks-source [amd64] (cosmic-proposed/none) [5.1.0+dfsg-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: puppet-module-ovn [amd64] (cosmic-proposed/none) [13.1.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: ruby-websocket [amd64] (cosmic-proposed/none) [1.2.5-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libpdl-ccs-perl [amd64] (cosmic-proposed/none) [1.23.8-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: puppet-module-congress [amd64] (cosmic-proposed/none) [13.1.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: xcite [amd64] (cosmic-proposed/universe) [1.60-4] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libpdl-ccs-perl [i386] (cosmic-proposed/none) [1.23.8-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: puppet-module-gnocchi [amd64] (cosmic-proposed/none) [13.1.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: ironic-inspector [amd64] (cosmic-proposed/universe) [7.3.0-0ubuntu1] (no packageset)
[17:44] -queuebot:#ubuntu-release- New: accepted puppet-module-arioch-redis [amd64] (cosmic-proposed) [3.2.0-1]
[17:44] -queuebot:#ubuntu-release- New: accepted puppet-module-gnocchi [amd64] (cosmic-proposed) [13.1.0-1]
[17:44] -queuebot:#ubuntu-release- New: accepted puppet-module-congress [amd64] (cosmic-proposed) [13.1.0-1]
[17:44] -queuebot:#ubuntu-release- New: accepted puppet-module-ovn [amd64] (cosmic-proposed) [13.1.0-1]
[17:45] -queuebot:#ubuntu-release- New: accepted c-sig [amd64] (cosmic-proposed) [3.8-22]
[17:45] -queuebot:#ubuntu-release- New: accepted ruby-turbolinks-source [amd64] (cosmic-proposed) [5.1.0+dfsg-1]
[17:45] -queuebot:#ubuntu-release- New: accepted senlin [amd64] (cosmic-proposed) [6.0.0~b2-0ubuntu1]
[17:45] -queuebot:#ubuntu-release- New: accepted ironic-inspector [amd64] (cosmic-proposed) [7.3.0-0ubuntu1]
[17:45] -queuebot:#ubuntu-release- New: accepted xcite [amd64] (cosmic-proposed) [1.60-4]
[17:45] -queuebot:#ubuntu-release- New: accepted ruby-websocket [amd64] (cosmic-proposed) [1.2.5-1]
[17:47] -queuebot:#ubuntu-release- New: accepted libpdl-ccs-perl [amd64] (cosmic-proposed) [1.23.8-1]
[17:47] -queuebot:#ubuntu-release- New: accepted libpdl-ccs-perl [i386] (cosmic-proposed) [1.23.8-1]
[18:07] <doko> ginggs: r-base:  r-cran-rmarkdown/armhf and /s390x, r-cran-yaml/i386 r-cran-memoise/armhf  still failing. did you look at any of those?
[18:07] <doko> no debian reports yet
[18:08] <doko> r-cran-rmarkdown is a leaf package
[18:37] -queuebot:#ubuntu-release- New binary: monero [amd64] (cosmic-proposed/universe) [0.12.2.0~dfsg-1] (no packageset)
[18:51] <LocutusOfBorg> hello chrisccoulson, are you aware of the dh-cargo/amd64 unsatisfiable Depends: cargo (>= 0.27.0-2)  issue?
[19:15] <ginggs> doko:  r-cran-rmarkdown/armhf and /s390x is due to missing haskell/pandoc
[19:16] <ginggs> doko:  r-cran-yaml/i386 is a regression due to new r-cran-yaml, r-cran-memoise is a alignment regression due to new r-cran-memoise - none are caused by the new r-base
[19:55] -queuebot:#ubuntu-release- New: accepted monero [amd64] (cosmic-proposed) [0.12.2.0~dfsg-1]
[20:22] <ginggs> would someone please 'force-badtest pyfai/0.15.0+dfsg1-1/amd64' ?  It passed once by accident on 2018-06-01  http://autopkgtest.ubuntu.com/packages/p/pyfai/cosmic/amd64
[21:06]  * enyc sneezes....
[22:38] -queuebot:#ubuntu-release- New source: qemu-ovmf-secureboot (cosmic-proposed/primary) [1.1.2-0ubuntu1]