Project Number Date
test_Tails_ISO_stable 5021 12 Aug 2024, 14:04

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 37:22.243 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:3.794
Before features/support/hooks.rb:269 0.006
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.567
When I start Tails from USB drive "old" with network unplugged 1:29.284
Then the boot device has safe access rights 2.745
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 9.126
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.886
Before features/support/hooks.rb:269 0.006
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:20.958
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.939
And I take note of which tps features are available 1.354
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.349
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.171
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.842
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.959
When I write some files expected to persist 1.732
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 2.763
And I take note of which tps features are available 0.372
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.112
After features/support/hooks.rb:326 0.088
After features/support/hooks.rb:100 0.017
Tags: @product
2:25.607
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.787
And I log in to a new session 18.789
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.403
Then the running Tails is installed on USB drive "to_upgrade" 16.999
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 3.531
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.306
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.626
Then all tps features from the old Tails version are active 1.465
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 2.908
And the expected persistent files created with the old Tails version are present in the filesystem 1.312
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25:32.158
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.304
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.112
And Tor is ready 21.310
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.725
Given I shutdown Tails and wait for the computer to power off 8.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.216
Then Tails is running version 6.2~testoverlayfs 0.031
And all tps features are active 2.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.069
And Tor is ready 14.248
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.298
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.986
Given I shutdown Tails and wait for the computer to power off 4.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:56.553
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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/common_steps.rb:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:301: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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
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
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 10.878 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:08:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5021/artifact/build-artifacts/02:08:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5021/artifact/build-artifacts/02:08:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5021/artifact/build-artifacts/02:08:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
31.318
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.530
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.780
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 15.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.010
After features/support/hooks.rb:326 1.104
After features/support/hooks.rb:100 0.000