Feature #12287
Deal with April 2017 false positive scenarios
0%
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
History
#1 Updated by anonym 2017-03-04 10:46:57
- 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 intrigeri 2017-04-18 15:08:49
- Target version changed from Tails_3.0 to Tails_3.0~rc1
#4 Updated by intrigeri 2017-04-19 14:20:08
Whenever you do this work, it would be very nice to look for issues I’ve listed on Feature #11983: knowing whether we also see them on feature/stretch would help a lot evaluate the impact of Feature #5630.
#5 Updated by intrigeri 2017-05-16 13:30:09
- blocks
Feature #12536: Have the devel branch based on Stretch added
#6 Updated by anonym 2017-05-16 16:56:27
Also look at feature/5630-deterministic-builds
.
#7 Updated by intrigeri 2017-05-18 17:37:55
- blocked by deleted (
)Feature #12536: Have the devel branch based on Stretch
#8 Updated by intrigeri 2017-05-19 10:39:02
- Status changed from Confirmed to Rejected
- Assignee deleted (
anonym)
I lost the feature/stretch data by mistake.