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

[Iain Lane]

Hmm, yeah, for me it failed 4 times out of 100 runs. That's better than
the previous state which failed every time I tried.

Thanks for the pycodestyle - I didn't run that one.

Ah, when it fails we see

  autopkgtest-virt-lxd: DBG: hook_wait_reboot: container now up for 4.0
- has not rebooted (initial uptime 10.0)

I think that's a lexicographic comparison issue. We should return a
float from get_uptime().

Force pushed to the same place. I'm currently running the testsuite with
AUTOPKGTEST_TEST_LXD set, will comment again if there's any regression.

-- 
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:
  In Progress

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