Project Number Date
test_Tails_ISO_stable 6692 25 Sep 2026, 12:12

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 17:20.758 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:3.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.305
When I start Tails from USB drive "old" with network unplugged 46.113
Then the boot device has safe access rights 2.361
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 3.538
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.021
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login 48.314
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.404
And I take note of which tps features are available 6.671
Then a Tails persistence partition exists on USB drive "old" 0.705
And I shutdown Tails and wait for the computer to power off 2.563
After features/support/hooks.rb:339 0.304
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.591
Then Tails is running from USB drive "old" 0.224
And all tps features are active 7.064
When I write some files expected to persist 1.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.546
And I take note of which tps features are available 6.531
And I shutdown Tails and wait for the computer to power off 2.611
# 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.221
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.678
And I log in to a new session 11.431
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.195
And I plug USB drive "to_upgrade" 2.186
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.456
Then the running Tails is installed on USB drive "to_upgrade" 18.209
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.592
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.724
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.315
And the expected persistent files created with the old Tails version are present in the filesystem 1.356
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
9:38.378
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.347
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.022
And Tor is ready 12.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.958
Given I shutdown Tails and wait for the computer to power off 7.776
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.931
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.199
When the network is plugged 0.032
And Tor is ready 10.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4:10.078
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.569
Given I shutdown Tails and wait for the computer to power off 3.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.926
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.663
And the file system changes introduced in version 6.3~testoverlayfs are present 0.261
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.030
And Tor is ready 10.036
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.811 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:44:57)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_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/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
23.326
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.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.952
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.000