Project Number Date
test_Tails_ISO_stable-flatpak 26 24 Sep 2026, 20:13

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 14:44.983 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
54.550
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.006
When I start Tails from USB drive "old" with network unplugged 38.122
Then the boot device has safe access rights 1.776
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.143
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.764
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 46.942
Then Tails is running from USB drive "old" 0.183
And I create a persistent partition 23.262
And I take note of which tps features are available 6.016
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.093
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.129
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.063
When I write some files expected to persist 1.141
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.111
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.582
And I take note of which tps features are available 6.015
And I shutdown Tails and wait for the computer to power off 2.537
# 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" 10.954
After features/support/hooks.rb:339 0.175
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.720
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 7.912
And I log in to a new session 10.814
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.551
Then the running Tails is installed on USB drive "to_upgrade" 17.384
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.432
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.882
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.003
Then all tps features from the old Tails version are active 1.043
And Tails is running from USB drive "to_upgrade" 0.182
And the boot device has safe access rights 2.035
And the expected persistent files created with the old Tails version are present in the filesystem 0.965
And all persistent directories from the old Tails version have safe access rights 1.577
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
7:22.797
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.166
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.023
And Tor is ready 13.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:2.893
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 5.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.216
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.189
When the network is plugged 0.033
And Tor is ready 10.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.395
Given I shutdown Tails and wait for the computer to power off 2.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.197
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.615
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.034
And Tor is ready 11.911
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.690 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:47:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_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/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
22.348
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.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 8.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.969
After features/support/hooks.rb:339 1.105
After features/support/hooks.rb:108 0.000