Project Number Date
test_Tails_ISO_devel 3816 17 May 2025, 10:10

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 38:46.278 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:9.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.301
When I start Tails from USB drive "old" with network unplugged 1:29.925
Then the boot device has safe access rights 3.294
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:330 6.958
After features/support/hooks.rb:100 0.020
Tags: @product
2:9.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:27.598
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.850
And I take note of which tps features are available 1.828
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.264
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.414
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.430
Then Tails is running from USB drive "old" 0.567
And all tps features are active 1.989
When I write some files expected to persist 1.727
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.317
After features/support/hooks.rb:330 0.089
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.806
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 without a persistent partition and stopped at Tails Greeter's login screen 9.261
And I log in to a new session 17.790
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.494
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.595
Then the running Tails is installed on USB drive "to_upgrade" 23.823
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:330 2.076
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.009
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.127
And the expected persistent files created with the old Tails version are present in the filesystem 1.305
And all persistent directories from the old Tails version have safe access rights 2.563
After features/support/hooks.rb:330 1.709
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25:56.897
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.164
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.882
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.445
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.065
And Tor is ready 23.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.690
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.934
Given I shutdown Tails and wait for the computer to power off 10.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.811
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.406
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.277
When the network is plugged 0.063
And Tor is ready 22.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.239
Given I shutdown Tails and wait for the computer to power off 4.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:56.776
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.860 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:09:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3816/artifact/build-artifacts/02:09:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3816/artifact/build-artifacts/02:09:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3816/artifact/build-artifacts/02:09:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
41.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.393
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.588
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 22.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.000
After features/support/hooks.rb:330 1.059
After features/support/hooks.rb:100 0.000