Project

General

Profile

Bug #11589

Bug #10288: Fix newly identified issues to make our test suite more robust and faster

Time syncing over bridge is fragile

Added by bertagaz over 3 years ago. Updated 3 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
-
Start date:
07/22/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

While referencing the test suite failure in Jenkins for 2016 June (see #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 #10288, and the long term plan is #5774. But until this is implemented (or any other shorter term plan), this scenario is marked as fragile.

stable_319.log View (747 KB) bertagaz, 07/22/2016 02:35 AM

devel_373.log View (748 KB) bertagaz, 07/22/2016 02:36 AM

Related issues

Related to Tails - Feature #5774: Robust time syncing In Progress 05/17/2015
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

Associated revisions

Revision 0e029825 (diff)
Added by bertagaz over 3 years ago

Test suite: mark time syncing over bridge scenario as fragile.

Refs: #11589

Revision f32fccfd (diff)
Added by bertagaz over 3 years ago

Revert "Test suite: mark time syncing over bridge scenario as fragile."

This reverts commit 0e0298253f01ff971ff9d454343515fce0f1adde.

Refs: #11589

Revision 02367ddf (diff)
Added by intrigeri over 3 years ago

Test suite: mark "Using bridges" scenario as fragile (refs: #11589).

Revision ab4eec88 (diff)
Added by intrigeri over 3 years ago

Revert "Test suite: mark "Using bridges" scenario as fragile (refs: #11589)."

This reverts commit 02367ddfd5118a30a28b359d8876a4868163cd07.

History

#1 Updated by bertagaz over 3 years ago

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

Marking scenario as fragile.

#2 Updated by bertagaz over 3 years ago

  • Description updated (diff)

#3 Updated by bertagaz over 3 years ago

#4 Updated by intrigeri over 3 years ago

  • 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 over 3 years ago

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

#6 Updated by intrigeri over 3 years ago

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

#7 Updated by intrigeri 3 months ago

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

(Context: #5394#note-32)

#8 Updated by intrigeri 3 months ago

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

#9 Updated by intrigeri 3 months ago

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

Let's see if this is still a problem once #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: #5394#note-35

Also available in: Atom PDF