Public bug reported:
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.
** Affects: auto-package-testing
Importance: Undecided
Status: New
** Description changed:
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.
+ we've detected a perma-looping test, and ideally a perma-looping test
+ would be caught and killed, and marked appropriately as a failure.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058918
Title:
Improve heuristics in detecting packages causing looping
Status in Auto Package Testing:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058918/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : [email protected]
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
