Feature #9515

Improve test suite robustness vs transient network errors

Added by anonym 2015-06-02 13:48:29 . Updated 2015-11-04 10:46:59 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Test suite
Target version:
Tails_1.7
Start date:
2015-06-02
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The amount of false positives we get from tests failing due to transient network errors (e.g. Tor being slow, Exit node blocking, the live destination servers having issues etc.) is already problematic, and is blocking deployment in our Jenkins infrastructure (Feature #8539). Let’s make the tests must susceptible to these issues simulate a user retrying (in a suitable manner) whenever such errors occur.

Subtasks

Feature #9516: Restart Tor if bootstrapping stalls for too long Resolved

100
Feature #9517: Retry connecting to OFTC when it fails Resolved

100
Feature #9518: Retry with new OpenPGP key server pool member when they misbehave Resolved

100
Feature #9668: Retry whois request on "WHOIS LIMIT EXCEEDED" Resolved

100
Bug #9715: Retry wget in the test suite when failing to resolve a host Resolved

100

Related issues

Related to Tails - Bug #9478: How to deal with transient network errors in the test suite? Resolved 2015-05-27

History

#1 Updated by anonym 2015-06-02 14:08:24

  • related to Bug #9478: How to deal with transient network errors in the test suite? added

#2 Updated by anonym 2015-06-02 14:11:35

  • blocks Feature #8539: Make the test suite robust enough to be run as part of a CI setup added

#3 Updated by anonym 2015-06-02 14:12:23

I couldn’t make this ticket a child of Feature #8539, adding it as a blocker then.

#4 Updated by anonym 2015-06-02 14:16:14

  • Assignee set to kytv
  • Target version set to Tails_1.4.1

Please change the milestone if 1.4.1 is too optimistic.

#5 Updated by anonym 2015-06-02 14:19:33

  • blocks #8538 added

#6 Updated by intrigeri 2015-06-04 21:22:31

Maybe this should be a subticket of Feature #8539, instead of a ticket that blocks it? If you don’t mind, I’ll just do it.

#7 Updated by intrigeri 2015-06-04 21:24:20

  • related to deleted (Bug #9478: How to deal with transient network errors in the test suite?)

#8 Updated by intrigeri 2015-06-04 21:24:25

  • blocked by deleted (Feature #8539: Make the test suite robust enough to be run as part of a CI setup)

#9 Updated by intrigeri 2015-06-04 21:24:49

  • blocked by deleted (#8538)

#10 Updated by intrigeri 2015-06-04 21:27:25

#11 Updated by intrigeri 2015-06-04 21:27:56

  • related to Bug #9478: How to deal with transient network errors in the test suite? added

#12 Updated by intrigeri 2015-06-04 21:28:21

  • blocks #8538 added

#13 Updated by intrigeri 2015-06-04 21:29:52

Sorry for the noise, I missed the fact that you had unsuccessfully tried to do it. Now done. I had to delete all ticket relationships for this one and each of its subtickets first. Now re-adding them.

#14 Updated by kytv 2015-06-28 13:05:21

  • Target version changed from Tails_1.4.1 to Tails_1.5

#15 Updated by intrigeri 2015-07-01 10:21:59

  • Description updated

#16 Updated by kytv 2015-07-09 06:30:18

  • related to Bug #9715: Retry wget in the test suite when failing to resolve a host added

#17 Updated by kytv 2015-07-09 06:31:12

  • related to deleted (Bug #9715: Retry wget in the test suite when failing to resolve a host)

#18 Updated by kytv 2015-08-04 04:01:32

  • Target version changed from Tails_1.5 to Tails_1.6

#19 Updated by kytv 2015-09-22 03:49:31

  • Target version changed from Tails_1.6 to Tails_1.7

#20 Updated by intrigeri 2015-09-22 06:05:05

> […] is already problematic, and is blocking deployment in our Jenkins infrastructure (Feature #8539)

This deployment is happening.

#21 Updated by kytv 2015-11-04 10:46:59

  • Status changed from Confirmed to Resolved
  • Assignee deleted (kytv)

Marking as resolved since all subtickets have been resolved.