Project Number Date
test_Tails_ISO_codespell 9 23 Jun 2025, 12:02

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 59 1 27 0 0 87 6 1 7 25:26.383 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
4:1.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.444
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.154
And I write an old version of the Tails USB image to disk "old" 1:1.845
When I start Tails from USB drive "old" with network unplugged 2:40.968
Then the boot device has safe access rights 4.450
And Tails is running from USB drive "old" 0.958
And there is no persistence partition on USB drive "old" 0.933
And process "udev-watchdog" is running 0.568
And udev-watchdog is monitoring the correct device 1.341
And I unplug USB drive "old" 8.776
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.020
Tags: @product
4:6.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login 2:38.638
Then Tails is running from USB drive "old" 0.670
And I create a persistent partition 1:4.855
And I take note of which tps features are available 4.837
Then a Tails persistence partition exists on USB drive "old" 7.324
And I shutdown Tails and wait for the computer to power off 9.654
After features/support/hooks.rb:330 0.463
After features/support/hooks.rb:100 0.098
Tags: @product
5:38.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.090
Given a computer 4.727
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:9.901
Then Tails is running from USB drive "old" 1.512
And all tps features are active 2.543
When I write some files expected to persist 6.492
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.061
And all persistence configuration files have safe access rights 1.571
And all persistent directories from the old Tails version have safe access rights 5.818
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 7.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 56.906
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.015
Tags: @product
4:33.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.533
And I log in to a new session 37.903
And I clone USB drive "old" to a new USB drive "to_upgrade" 13.917
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:17.293
Then the running Tails is installed on USB drive "to_upgrade" 58.651
And I unplug USB drive "to_upgrade" 0.269
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 3.986
After features/support/hooks.rb:100 0.000
Tags: @product
4:57.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.073
Given a computer 0.590
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:19.618
Then all tps features from the old Tails version are active 2.758
And Tails is running from USB drive "to_upgrade" 4.142
And the boot device has safe access rights 12.108
And the expected persistent files created with the old Tails version are present in the filesystem 3.588
And all persistent directories from the old Tails version have safe access rights 14.325
After features/support/hooks.rb:330 2.609
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
51.728
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.023
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.320
And no SquashFS delta is installed 3.233
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 4.087
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.635
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.968
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.328
When the network is plugged 0.142
And Tor is ready 17.012
try_for() 
try_for() timeout expired (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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~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.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
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 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
# 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 7.017 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:04:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/9/artifact/build-artifacts/03:04:50_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/9/artifact/build-artifacts/03:04:50_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/9/artifact/build-artifacts/03:04:50_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/9/artifact/build-artifacts/03:04:50_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:18.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.789
And the signing key used by the Upgrader is outdated 1.408
But a current signing key is available on our website 0.000
When the network is plugged 1.849
And Tor is ready 40.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.028
After features/support/hooks.rb:330 1.733
After features/support/hooks.rb:100 0.000