Improve heuristics in detecting packages causing looping
Bug #2058918 reported by
Tim Andersson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Auto Package Testing |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
We currently don't have a good way of detecting tests that have been looping forever. We need to improve this and at least add logging when we've detected a perma-looping test, and ideally a perma-looping test would be caught and killed, and marked appropriately as a failure.
| description: | updated |
Revision history for this message
| Skia (hyask) wrote | #1 |
| Changed in auto-package-testing: | |
| status: | New → Fix Released |
To post a comment you must log in.
Tests looping indefinitely has been worked on, and hasn't been seen in a while now. Closing this as "Fixed released"