Bug #17216
Make the test suite clean up after itself even in most tricky failure modes
Start date:
Due date:
% Done:
0%
Description
Goals:
- avoid leaving zombie processes behind (e.g. Xvfb, unclutter, tor processes started by Chutney, avconv, local services run by cucumber, etc.)
- drop the whole “reboot before running the test suite” dance in our CI (
Bug #10601,Bug #11295) - have CI nodes that can run both builds & tests, which would provide great performance improvements to our feedback loop: we often have build jobs in the queue while isotesters are idling, or test jobs in the queue while builders are idling
How to do so? Wrap the test suite with something that will track resources and clean them up, such as:
systemd-run, which could a not-super-expensive incremental step forward:Bug #11295#note-38- Docker, which would allow us to have multiple Jenkins executors on one single big node (instead of a number of isotesterN VMs with one executor each), resulting in better usage of our hardware resources:
Scope:
- Initially: our CI.
- Ideally, the solution would also work for developers who run the test suite locally.
- Ideally, the solution would not depend on Jenkins much, if at all, so we benefit from it even if we migrate to another kind of CI some day.
Subtasks
Related issues
| Related to Tails - Bug #16960: Make our CI feedback loop shorter | In Progress | ||
|
Related to Tails - |
Needs Validation | 2015-11-23 | |
|
Related to Tails - |
Resolved | 2016-03-31 | |
|
Related to Tails - |
Resolved | 2017-11-10 | |
|
Related to Tails - |
Resolved |
History
#1 Updated by intrigeri 2019-11-09 10:59:07
- related to Bug #16960: Make our CI feedback loop shorter added
#2 Updated by intrigeri 2019-11-09 10:59:13
- related to
Bug #10601: isotesterN:s are sometimes put offline and never back online added
#3 Updated by intrigeri 2019-11-09 10:59:19
- related to
Bug #11295: Test jobs sometimes get scheduled on a busy isotester while there are available ones added
#4 Updated by intrigeri 2019-11-09 11:00:25
- related to
Bug #14948: zombie processes when running the test suite added
#5 Updated by intrigeri 2019-12-15 09:00:46
- Subject changed from Make the test suite clean up after itself even in most failure modes to Make the test suite clean up after itself even in most tricky failure modes
#7 Updated by intrigeri 2019-12-27 16:28:30
- Description updated
#8 Updated by intrigeri 2019-12-27 16:30:41
- Description updated
#9 Updated by intrigeri 2020-04-15 10:31:32
- related to
Bug #17551: Test suite has defunct processes after sikuli removal added