Bug #11589

Time syncing over bridge is fragile

Added by bertagaz 2016-07-22 02:39:56 . Updated 2019-11-08 19:14:14 .

Test suite
Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


While referencing the test suite failure in Jenkins for 2016 June (see Bug #11087), we noticed two failures of the time syncing over bridge scenario. It sometimes happens in this case that tordate fails to set the time. That was already discussed a bit in Bug #10288, and the long term plan is Feature #5774. But until this is implemented (or any other shorter term plan), this scenario is marked as fragile.


stable_319.log (765275 B) bertagaz, 2016-07-22 02:35:44
devel_373.log (765651 B) bertagaz, 2016-07-22 02:36:14


Related issues

Related to Tails - Feature #5774: Robust time syncing In Progress 2015-05-17
Related to Tails - Bug #5394: Time syncing can break Tor bootstrap when using several bridges with different certificate lifespans In Progress
Blocked by Tails - Bug #16792: Upgrade our Chutney fork Resolved


#1 Updated by bertagaz 2016-07-22 02:47:30

  • Feature Branch set to test/11589-time-syncing-over-bridge

Marking scenario as fragile.

#2 Updated by bertagaz 2016-07-22 02:52:18

  • Description updated

#3 Updated by bertagaz 2016-07-22 02:53:06

#4 Updated by intrigeri 2016-07-22 05:06:19

  • Target version deleted (Tails_2.6)

bertagaz: if there’s a good reason to set target version to 2.6 with no assignee, please revert this change (and explain).

#5 Updated by intrigeri 2016-07-22 05:53:48

  • Feature Branch changed from test/11589-time-syncing-over-bridge to wip/test/11589-time-syncing-over-bridge

#6 Updated by intrigeri 2016-07-29 07:48:56

  • related to Bug #5394: Time syncing can break Tor bootstrap when using several bridges with different certificate lifespans added

#7 Updated by intrigeri 2019-10-20 07:50:45

  • Assignee set to intrigeri
  • Target version set to Tails_4.1
  • Feature Branch deleted (wip/test/11589-time-syncing-over-bridge)

(Context: Bug #5394#note-32)

#8 Updated by intrigeri 2019-11-08 19:11:48

  • blocked by Bug #16792: Upgrade our Chutney fork added

#9 Updated by intrigeri 2019-11-08 19:14:14

  • Assignee deleted (intrigeri)
  • Target version deleted (Tails_4.1)

Let’s see if this is still a problem once Bug #16792 is merged.

I’m dropping this for my plate because I think my original motivation for assigning this ticket to myself was based on erroneous assumptions: Bug #5394#note-35