Bug #11589
Bug #10288: Fix newly identified issues to make our test suite more robust and faster
Time syncing over bridge is fragile
0%
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.
Related issues
Associated revisions
Test suite: mark time syncing over bridge scenario as fragile.
Refs: #11589
Revert "Test suite: mark time syncing over bridge scenario as fragile."
This reverts commit 0e0298253f01ff971ff9d454343515fce0f1adde.
Refs: #11589
Test suite: mark "Using bridges" scenario as fragile (refs: #11589).
Revert "Test suite: mark "Using bridges" scenario as fragile (refs: #11589)."
This reverts commit 02367ddfd5118a30a28b359d8876a4868163cd07.
History
#1 Updated by bertagaz about 3 years ago
- Feature Branch set to test/11589-time-syncing-over-bridge
Marking scenario as fragile.
#2 Updated by bertagaz about 3 years ago
- Description updated (diff)
#3 Updated by bertagaz about 3 years ago
- Related to Feature #5774: Robust time syncing added
#4 Updated by intrigeri about 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 about 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 about 3 years ago
- Related to Bug #5394: Fix time syncing in bridge mode added