Public bug reported:
Hi,
as all packagers every now and then I debug cases that unexpectedly fail dep8
tests.
All of us especially love issues that at first seems unreproducible locally but
always (or even only sometimes) trigger on Launchpad.
In at least two occasions I had OOM killers kick in and I wondered how
much easier I could have found that if there would be something in the
logs about that.
So I wanted to ask if any of the following would appear reasonable to implement:
1) In the FAIL case making a few default checks and put it to the logs (can be
a dmesg | grep -i oom to start, but I'm sure over time people would come up
with more).
2) dmesg as default test artifact for every Test; run after the test is
over (maybe only on FAIL) and added to artifacts.
3) Now a bit hardcore, but maybe the de-facto super-debug-artifact for
FAIL cases could be to (in that case) install and run sosreport and add
the generated tgz as artifact.
** Affects: autopkgtest (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- auto-check for oom on Fails
+ check for common issues on Failed tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663497
Title:
check for common issues on Failed tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1663497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
