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

2024-07-29 Thread Skia
We don't run Trusty tests on armhf anymore. ** Changed in: auto-package-testing Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654025 Title: trusty/armhf dkms tests

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

2017-09-18 Thread Launchpad Bug Tracker
This bug was fixed in the package autopkgtest - 5.0 --- autopkgtest (5.0) unstable; urgency=medium [ Martin Pitt ] * Drop obsolete adt-* CLI autopkgtest 4.0 with its "autopkgtest" program has been around for a year, Debian's and Ubuntu's CI moved to that, and the Debian 9.

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

2017-01-22 Thread Iain Lane
Thanks pitti! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654025 Title: trusty/armhf dkms tests are killing workers To manage notifications about this bug go to: https://bugs.launchpad.net/auto-

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

2017-01-22 Thread Martin Pitt
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=11d05a9ce ** Changed in: autopkgtest (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

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

2017-01-22 Thread 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.

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

2017-01-21 Thread 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 (ini

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

2017-01-21 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654025 Title: trusty/armhf dkms tests are killing workers To manage notifications about this bug go to: https://bugs.launchpad.ne

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

2017-01-21 Thread Martin Pitt
** Changed in: autopkgtest (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654025 Title: trusty/armhf dkms tests are killing workers To manage notification

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

2017-01-21 Thread Martin Pitt
Hello Iain, your patch had a few tests/pycodestyle errors, and I squashed them together. However, when testing this I sometimes run into a timeout: $ runner/autopkgtest tests/testpkg-reboot -- lxd autopkgtest/ubuntu/zesty/amd64 autopkgtest [10:43:57]: git checkout: 77cd1c3 doc/README.package-test

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

2017-01-21 Thread Martin Pitt
** Also affects: autopkgtest (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654025 Title: trusty/armhf dkms tests are killing workers To manage