[Bug 1654025] Re: trusty/armhf dkms tests are killing workers

[Martin Pitt]

string vs. float comparison makes sense indeed. It could also be that by
testpkg-reboot/'s nature, rebooting is pretty much the first thing it
does, so it could happen that the uptime before reboot is even smaller
than the first time we check after reboot -- but that's a bit academic
in practice.

This works fairly well now, so I pushed this with a small addition to
get_uptime() to redirect stderr to /dev/null. Otherwise you get some
potentially misleading "error: Container is not running." messages.
Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1654025

Title:
  trusty/armhf dkms tests are killing workers

Status in Auto Package Testing:
  New
Status in autopkgtest package in Ubuntu:
  Fix Committed

Bug description:
  We noticed earlier today that almost all armhf (lxd) workers were
  dead.

  After a lot of poking, it seems to me that they are being killed when
  running dkms tests for the kernel in trusty-proposed.

  When trying to download the source package, we get:

  > autopkgtest [15:14:36]: ERROR: erroneous package: got 0 lines of results from extract where 4 expected: []
  > autopkgtest: DBG: testbed stop
  > autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.Mco1QJ
  > autopkgtest: DBG: sending command to testbed: close
  > blame: nvidia-graphics-drivers-340
  > badpkg: got 0 lines of results from extract where 4 expected: []

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1654025/+subscriptions