Bug #10440
Time syncing scenarios are fragile
Start date:
2015-10-28
Due date:
% Done:
100%
Description
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2016-04-15 | |
Blocked by Tails - |
Resolved | 2015-11-06 |
History
#1 Updated by kytv 2015-10-28 07:02:42
- Parent task set to Bug #10288
#2 Updated by kytv 2015-10-28 07:06:21
- Status changed from Confirmed to In Progress
- Feature Branch set to kytv/test/10440-time-syncing-tests-are-fragile
#3 Updated by intrigeri 2015-10-31 05:52:52
- blocks #8668 added
#4 Updated by intrigeri 2015-11-06 06:07:20
- Assignee set to anonym
- Deliverable for set to 270
#5 Updated by anonym 2015-11-06 12:20:08
- Target version set to Tails_2.3
#6 Updated by anonym 2016-02-20 14:23:20
- Target version deleted (
Tails_2.3) - Deliverable for deleted (
270)
#7 Updated by anonym 2016-05-14 06:18:34
- Target version set to Tails_2.4
- % Done changed from 0 to 50
- QA Check set to Dev Needed
- Feature Branch changed from kytv/test/10440-time-syncing-tests-are-fragile to test/9521-chutney
- Type of work changed from Code to Wait
Since “tordate”, the actual Tails feature, is essentially broken, let’s kill these scenarios. Let’s spend all energy in this category on fixing Feature #5774 (Robust time syncing).
#8 Updated by anonym 2016-05-14 06:18:52
- blocked by
Feature #9521: Use the chutney Tor network simulator in our test suite added
#9 Updated by anonym 2016-05-14 06:19:38
(Details for this decision: Feature #9521#note-46)
#10 Updated by intrigeri 2016-05-18 15:16:32
- blocked by deleted (
#8668)
#11 Updated by intrigeri 2016-05-18 15:29:02
- Feature Branch changed from test/9521-chutney to test/10497-tor-bootstrap-is-fragile
test/10497-tor-bootstrap-is-fragile drops the fragile flags on those tests, so once it’s merged, we can mark this ticket as fix committed :)
#12 Updated by intrigeri 2016-05-18 15:29:15
- blocked by
Bug #10497: wait_until_tor_is_working helper is fragile added
#13 Updated by intrigeri 2016-05-26 09:10:18
- Subject changed from Time syncing tests are fragile to Time syncing scenarios are fragile
#14 Updated by anonym 2016-06-02 12:46:12
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Dev Needed to Pass
intrigeri wrote:
> test/10497-tor-bootstrap-is-fragile drops the fragile flags on those tests, so once it’s merged, we can mark this ticket as fix committed :)
Doing so.
#15 Updated by anonym 2016-06-08 01:31:38
- Status changed from Fix committed to Resolved