Given
I have started Tails without network from a USB drive with a persistent partition enabled and logged in
11.898
And
no SquashFS delta is installed
0.575
And
Tails is fooled to think that version 6.0~testoverlayfs was initially installed
0.293
And
Tails is fooled to think it is running version 6.0~testoverlayfs
0.071
And
the file system changes introduced in version 6.2~testoverlayfs are not present
0.283
And
the file system changes introduced in version 6.3~testoverlayfs are not present
0.473
When
the network is plugged
0.067
Then
I am proposed to install an incremental upgrade to version 6.2~testoverlayfs
6.786
And
I can successfully install the incremental upgrade to version 6.2~testoverlayfs
11.732
Given
I shutdown Tails and wait for the computer to power off
8.688
When
I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled
1:35.876
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:451:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:450:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then
Tails is running version 6.2~testoverlayfs
0.000
And
all tps features are active
0.000
And
the file system changes introduced in version 6.2~testoverlayfs are present
0.000
And
only the 6.2~testoverlayfs SquashFS delta is installed
0.000
Given
Tails system time is magically synchronized
0.000
And
Tails is fooled to think that version 6.1~testoverlayfs was initially installed
0.000
When
the network is plugged
0.000
Then
I am proposed to install an incremental upgrade to version 6.3~testoverlayfs
0.000
And
I can successfully install the incremental upgrade to version 6.3~testoverlayfs
0.000
Given
I shutdown Tails and wait for the computer to power off
0.000
When
I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled
0.000
Then
Tails is running version 6.3~testoverlayfs
0.000
And
all tps features are active
0.000
And
the file system changes introduced in version 6.3~testoverlayfs are present
0.000
And
only the 6.3~testoverlayfs SquashFS delta is installed
0.000
Given
Tails system time is magically synchronized
0.000
And
Tails is fooled to think that version 6.1~testoverlayfs was initially installed
0.000
When
the network is plugged
0.000
Then
the Upgrader considers the system as up-to-date
0.000
And
I successfully start the Unsafe Browser
0.000
And
the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot
0.000