check for common issues on Failed tests
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| autopkgtest (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
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-
| summary: |
- auto-check for oom on Fails + check for common issues on Failed tests |
| Martin Pitt (pitti) wrote | #1 |
| Christian Ehrhardt (paelzer) wrote | #2 |
Bug 1288529 is a more generic approach to this, which doesn't hardcode knowledge about journals, sosreports, etc. into autopkgtest itself, and makes it configurable through the CI system.
Please note that when designing this you make sure that you don't collect large logs for every failure. We run hundreds or sometimes thousands of tests every day, and their artifacts all need to be stored. So an sosreport-style tarball which is in the magnitude of a megabyte (or more?) seems prohibitively expensive to collect always.