Feature #12287

Deal with April 2017 false positive scenarios

Added by anonym about 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_3.0~rc1
Start date:
2017-04-05
Due date:
2017-05-05
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

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 about 8 years ago

  • Category set to Continuous Integration

#2 Updated by anonym about 8 years ago

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 about 8 years ago

  • Target version changed from Tails_3.0 to Tails_3.0~rc1

#4 Updated by intrigeri about 8 years ago

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 about 8 years ago

#6 Updated by anonym about 8 years ago

Also look at feature/5630-deterministic-builds.

#7 Updated by intrigeri about 8 years ago

  • blocked by deleted (Feature #12536: Have the devel branch based on Stretch)

#8 Updated by intrigeri about 8 years ago

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)

I lost the feature/stretch data by mistake.