Project Number Date
test_Tails_ISO_devel 3790 28 Apr 2025, 13:55

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 40:51.562 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:24.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.278
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 34.854
When I start Tails from USB drive "old" with network unplugged 1:43.529
Then the boot device has safe access rights 3.401
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:330 3.817
After features/support/hooks.rb:100 0.012
Tags: @product
2:18.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:33.111
Then Tails is running from USB drive "old" 0.440
And I create a persistent partition 32.112
And I take note of which tps features are available 2.902
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.942
After features/support/hooks.rb:330 0.244
After features/support/hooks.rb:100 0.012
Tags: @product
3:21.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 1.315
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.080
Then Tails is running from USB drive "old" 0.526
And all tps features are active 4.055
When I write some files expected to persist 4.571
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.566
And all persistent directories from the old Tails version have safe access rights 2.702
And I take note of which tps features are available 0.522
And I shutdown Tails and wait for the computer to power off 6.505
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.137
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.076
And I log in to a new session 22.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.183
And I plug USB drive "to_upgrade" 2.591
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.512
Then the running Tails is installed on USB drive "to_upgrade" 29.877
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.351
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.365
Then all tps features from the old Tails version are active 1.958
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.910
And the expected persistent files created with the old Tails version are present in the filesystem 1.760
And all persistent directories from the old Tails version have safe access rights 2.943
After features/support/hooks.rb:330 1.556
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
26:38.607
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.229
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.267
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.088
And Tor is ready 22.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.424
Given I shutdown Tails and wait for the computer to power off 11.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.177
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.817
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.348
When the network is plugged 0.076
And Tor is ready 49.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.146
Given I shutdown Tails and wait for the computer to power off 4.294
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:5.422
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:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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:330 10.894 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:15:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
46.034
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 24.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.990
After features/support/hooks.rb:330 1.996
After features/support/hooks.rb:100 0.000