summaryrefslogtreecommitdiffstats
path: root/features/usb_upgrade.feature
diff options
context:
space:
mode:
authoranonym <anonym@riseup.net>2017-02-02 14:57:38 +0100
committeranonym <anonym@riseup.net>2017-02-02 15:01:39 +0100
commite76536e6ecbd0e93b13d9b342120ac420a2b1ef3 (patch)
tree1f240eda007b755228d965f6d119a7d81a18fde2 /features/usb_upgrade.feature
parentf7594f97cf280817d8fefc6459dcf68cc6595a99 (diff)
Test suite: fix the incremental upgrade test.
Beside the image bumping due to the new font we use in Stretch, we also take steps making Tor bootstrap more reliable in the upgraded system. It used to be unreliable because the IUK sets a very wrong release date, and we use it in our time syncing.
Diffstat (limited to 'features/usb_upgrade.feature')
-rw-r--r--features/usb_upgrade.feature4
1 files changed, 3 insertions, 1 deletions
diff --git a/features/usb_upgrade.feature b/features/usb_upgrade.feature
index f73f634..fb2e3c7 100644
--- a/features/usb_upgrade.feature
+++ b/features/usb_upgrade.feature
@@ -167,8 +167,10 @@ Feature: Upgrading an old Tails USB installation
Then Tails is running version 1.1~test
And all persistence presets are enabled
And the file system changes introduced in version 1.1~test are present
+ # Our IUK sets a release date that can make Tor bootstrapping impossible
+ Given Tails system time is magically synchronized
When the network is plugged
- And the network connection is ready within 30 seconds
+ And Tor is ready
And all notifications have disappeared
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser