Project Number Date
test_Tails_ISO_stable 6691 24 Sep 2026, 15:11

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 13:42.892 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
1:4.709
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.956
When I start Tails from USB drive "old" with network unplugged 46.466
Then the boot device has safe access rights 2.551
And Tails is running from USB drive "old" 0.185
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:339 1.205
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.081
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 50.399
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 24.712
And I take note of which tps features are available 6.866
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 4.147
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.805
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.765
Then Tails is running from USB drive "old" 0.254
And all tps features are active 7.693
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.869
And I take note of which tps features are available 6.887
And I shutdown Tails and wait for the computer to power off 4.097
# 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" 12.483
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.017
Tags: @product
2:15.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.427
And I log in to a new session 12.053
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.955
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.923
Then the running Tails is installed on USB drive "to_upgrade" 19.321
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 0.791
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.872
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.166
Then all tps features from the old Tails version are active 1.263
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.250
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:339 0.982
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
5:38.711
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.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.649
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.040
And Tor is ready 12.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.050
Given I shutdown Tails and wait for the computer to power off 5.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.744
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.538
And the file system changes introduced in version 6.2~testoverlayfs are present 0.174
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.174
When the network is plugged 0.034
And Tor is ready 10.858
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.100
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.094
Given I shutdown Tails and wait for the computer to power off 3.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.663
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.983
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.030
And Tor is ready 10.681
Then the Upgrader considers the system as up-to-date 2:0.000
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.866 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:55:42)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_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/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
20.546
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.343
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.284
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.000