Bug #12648
Deal with July 2017 false positive CI notifications
Start date:
2017-06-07
Due date:
% Done:
100%
Description
Gather statistics about CI notifications since Feature #11355 brought them back online, then see how it goes and decide what to do.
Subtasks
Related issues
Related to Tails - Feature #11355: Re-enable Jenkins notifications on ISO build/test failure | In Progress | 2017-08-28 |
History
#1 Updated by bertagaz 2017-06-07 08:50:17
- related to Feature #11355: Re-enable Jenkins notifications on ISO build/test failure added
#2 Updated by bertagaz 2017-06-07 08:53:52
- Subject changed from Deal with Juky 2017 false positive CI notifications to Deal with July 2017 false positive CI notifications
#3 Updated by intrigeri 2017-06-07 13:34:41
- Deliverable for set to SponsorS_Internal
#4 Updated by intrigeri 2017-06-30 16:15:44
- Deliverable for deleted (
SponsorS_Internal)
#5 Updated by intrigeri 2017-06-30 16:17:19
- blocks
Feature #13239: Core work 2017Q3: Test suite maintenance added
#6 Updated by intrigeri 2017-06-30 19:15:23
- blocked by deleted (
)Feature #13239: Core work 2017Q3: Test suite maintenance
#7 Updated by intrigeri 2017-06-30 19:15:32
- Deliverable for set to SponsorS_Internal
#8 Updated by bertagaz 2017-08-01 12:26:36
- Status changed from Confirmed to Resolved
- Assignee deleted (
bertagaz) - % Done changed from 0 to 100
So in July, test failure notifications have been disabled, no stats for this one.
Only intrigeri received emails (apart from tails-rm@ for base branches) about build failures, due to Bug #13530.
Not much to act on right now. Next step is to get test runs in Jenkins stable enough to reactivate test failure notifications. So that’s related to Feature #12290.