Project Number Date
test_Tails_ISO_21790-tor-0.4.9.13 1 24 Sep 2026, 16:49

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:0.523 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:14.418
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.867
When I start Tails from USB drive "old" with network unplugged 55.312
Then the boot device has safe access rights 2.510
And Tails is running from USB drive "old" 0.185
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.638
After features/support/hooks.rb:108 0.054
Tags: @product
1:33.994
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 55.819
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.889
And I take note of which tps features are available 7.271
Then a Tails persistence partition exists on USB drive "old" 0.580
And I shutdown Tails and wait for the computer to power off 4.057
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.009
Tags: @product
1:45.683
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.648
Then Tails is running from USB drive "old" 0.261
And all tps features are active 8.534
When I write some files expected to persist 1.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.044
And I take note of which tps features are available 7.379
And I shutdown Tails and wait for the computer to power off 4.238
# 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.370
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.571
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.296
And I log in to a new session 12.001
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.537
Then the running Tails is installed on USB drive "to_upgrade" 20.338
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.986
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.480
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:7.114
Then all tps features from the old Tails version are active 1.342
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.583
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:339 0.695
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
5:34.745
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.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.278
And no SquashFS delta is installed 0.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.031
And Tor is ready 12.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.864
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.359
Given I shutdown Tails and wait for the computer to power off 6.926
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.212
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.667
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.225
When the network is plugged 0.033
And Tor is ready 11.123
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.904
Given I shutdown Tails and wait for the computer to power off 3.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.007
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.028
And Tor is ready 10.522
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.838 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:57:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.629
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.961
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.000