Project Number Date
test_Tails_ISO_stable-flatpak 27 25 Sep 2026, 19:58

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 84 1 2 0 0 87 6 1 7 12:47.662 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
59.752
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.954
When I start Tails from USB drive "old" with network unplugged 43.389
Then the boot device has safe access rights 1.736
And Tails is running from USB drive "old" 0.171
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.622
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 47.548
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 23.412
And I take note of which tps features are available 6.166
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 4.069
After features/support/hooks.rb:339 0.262
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.543
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.820
When I write some files expected to persist 1.292
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.241
And all persistent directories from the old Tails version have safe access rights 1.748
And I take note of which tps features are available 6.196
And I shutdown Tails and wait for the computer to power off 2.540
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.059
After features/support/hooks.rb:339 0.415
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.560
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.452
And I log in to a new session 10.606
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.605
And I plug USB drive "to_upgrade" 2.358
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.837
Then the running Tails is installed on USB drive "to_upgrade" 17.445
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.809
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.641
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 1.914
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.702
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
5:21.204
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.288
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.033
And Tor is ready 13.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.788
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.629
Given I shutdown Tails and wait for the computer to power off 5.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.821
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.446
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.089
# 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.164
When the network is plugged 0.036
And Tor is ready 10.174
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.889
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.212
Given I shutdown Tails and wait for the computer to power off 2.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.742
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.500
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.034
And Tor is ready 10.274
Then the Upgrader considers the system as up-to-date 2:0.002
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/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'
# 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:339 4.649 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:40:48)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.642
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 10.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.630
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.000