Feature #12288
Deal with May 2017 false positive scenarios
Start date:
2017-05-05
Due date:
2017-06-05
% Done:
100%
Description
As defined in Bug #10993, check is there are still some of them and tag them as fragile if any (see Bug #10288).
Subtasks
Related issues
|
Blocks Tails - |
Resolved | 2017-05-26 | |
|
Blocks Tails - |
Resolved | 2017-06-29 |
History
#1 Updated by anonym 2017-03-04 10:46:58
- Category set to Continuous Integration
#2 Updated by anonym 2017-04-06 16:15:22
Now that we are close to 3.0 and feature/stretch being merged, let’s down-prioritize new robustness issues in stable and devel in the sense that we ignore the issue unless we find proof that it also affects feature/stretch. This might mean that we ignore an issue that actually affects feature/stretch but isn’t visible due to something breaking earlier in the affected tests, but let’s prefer that risk over identifying and tracking issues that don’t affect Tails after Jessie.
#3 Updated by anonym 2017-06-01 16:46:51
- blocks
Feature #12604: Remove the feature/stretch Jenkins jobs added
#4 Updated by anonym 2017-06-12 16:07:23
- Target version changed from Tails_3.0 to Tails_3.1
#5 Updated by anonym 2017-06-29 13:32:32
- blocks
Feature #13239: Core work 2017Q3: Test suite maintenance added
#6 Updated by anonym 2017-07-06 14:15:05
- Target version changed from Tails_3.1 to Tails_3.2
#7 Updated by intrigeri 2017-07-06 14:17:38
- Status changed from Confirmed to Resolved
- Assignee deleted (
anonym) - Target version changed from Tails_3.2 to Tails_3.1
- % Done changed from 0 to 100
Dropping the ball: we now have a full month with many more Stretch test runs.