Project Number Date
test_Tails_ISO_stable 6229 24 Mar 2026, 18:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 11:43.456 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:15.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.090
When I start Tails from USB drive "old" with network unplugged 57.865
Then the boot device has safe access rights 2.737
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:331 1.377
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.262
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.258
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 24.157
And I take note of which tps features are available 0.744
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 8.327
After features/support/hooks.rb:331 0.600
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.950
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.617
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.017
When I write some files expected to persist 1.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 1.775
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 7.845
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.547
After features/support/hooks.rb:331 0.341
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.024
And I log in to a new session 12.011
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.664
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.483
Then the running Tails is installed on USB drive "to_upgrade" 14.886
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.319
After features/support/hooks.rb:100 0.000
Tags: @product
40.633
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 40.580
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:331 4.927 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:03:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6229/artifact/build-artifacts/01:03:14_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6229/artifact/build-artifacts/01:03:14_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6229/artifact/build-artifacts/01:03:14_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6229/artifact/build-artifacts/01:03:14_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:23.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.847
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.022
And Tor is ready 19.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.338
Given I shutdown Tails and wait for the computer to power off 14.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.219
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.054
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.226
When the network is plugged 0.015
And Tor is ready 21.169
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.784
Given I shutdown Tails and wait for the computer to power off 17.073
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.672
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.038
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.019
And Tor is ready 20.994
Then the Upgrader considers the system as up-to-date 0.102
# 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 4.084
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
23.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.385
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.046
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.014
And Tor is ready 15.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.000