Project Number Date
test_Tails_ISO_fix-homepage-image 3 08 Jul 2025, 10:49

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 71 1 15 0 0 87 6 1 7 25:33.394 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
3:6.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 44.541
When I start Tails from USB drive "old" with network unplugged 2:15.310
Then the boot device has safe access rights 4.247
And Tails is running from USB drive "old" 0.411
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 4.081
After features/support/hooks.rb:100 0.103
Tags: @product
3:24.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.091
Given a computer 0.641
And I start Tails from USB drive "old" with network unplugged and I login 2:12.321
Then Tails is running from USB drive "old" 0.516
And I create a persistent partition 53.863
And I take note of which tps features are available 2.694
Then a Tails persistence partition exists on USB drive "old" 0.739
And I shutdown Tails and wait for the computer to power off 14.085
After features/support/hooks.rb:330 0.259
After features/support/hooks.rb:100 0.044
Tags: @product
4:40.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.043
Given a computer 0.533
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:28.594
Then Tails is running from USB drive "old" 0.571
And all tps features are active 5.770
When I write some files expected to persist 4.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.345
And all persistence configuration files have safe access rights 0.594
And all persistent directories from the old Tails version have safe access rights 3.637
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 8.684
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 47.094
After features/support/hooks.rb:330 0.338
After features/support/hooks.rb:100 0.009
Tags: @product
3:41.242
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 11.902
And I log in to a new session 32.610
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.181
And I plug USB drive "to_upgrade" 2.707
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:8.721
Then the running Tails is installed on USB drive "to_upgrade" 42.683
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 3.611
After features/support/hooks.rb:100 0.000
Tags: @product
3:43.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:20.364
Then all tps features from the old Tails version are active 3.037
And Tails is running from USB drive "to_upgrade" 0.409
And the boot device has safe access rights 13.102
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 4.343
After features/support/hooks.rb:330 6.270
After features/support/hooks.rb:100 0.843
Tags: @product @automatic_upgrade
5:17.511
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.212
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.909
And no SquashFS delta is installed 0.304
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.561
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.083
And Tor is ready 30.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.917
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.595
Given I shutdown Tails and wait for the computer to power off 14.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:11.579
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 8.219
And the file system changes introduced in version 6.2~testoverlayfs are present 1.800
And only the 6.2~testoverlayfs SquashFS delta is installed 0.416
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.989
# 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 1.381
When the network is plugged 0.175
And Tor is ready 12.616
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:105:in `And Tor is ready'
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 9.517 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:07:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_fix-homepage-image/3/artifact/build-artifacts/02:07:17_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_fix-homepage-image/3/artifact/build-artifacts/02:07:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_fix-homepage-image/3/artifact/build-artifacts/02:07:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_fix-homepage-image/3/artifact/build-artifacts/02:07:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
1:39.476
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 47.797
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.890
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.591
And the signing key used by the Upgrader is outdated 0.696
But a current signing key is available on our website 0.000
When the network is plugged 0.930
And Tor is ready 31.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.298
After features/support/hooks.rb:330 1.316
After features/support/hooks.rb:100 0.000