Project Number Date
test_Tails_ISO_stable 6356 07 May 2026, 07:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 9:1.338 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
56.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.269
When I start Tails from USB drive "old" with network unplugged 38.830
Then the boot device has safe access rights 2.616
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.176
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.912
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 22.963
And I take note of which tps features are available 0.645
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 8.133
After features/support/hooks.rb:331 0.491
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.280
Then Tails is running from USB drive "old" 0.219
And all tps features are active 1.188
When I write some files expected to persist 1.364
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 1.828
And I take note of which tps features are available 0.232
And I shutdown Tails and wait for the computer to power off 7.864
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.750
After features/support/hooks.rb:331 0.519
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.347
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 7.872
And I log in to a new session 12.144
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.938
Then the running Tails is installed on USB drive "to_upgrade" 15.102
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 2.147
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.876
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.211
And all persistent directories from the old Tails version have safe access rights 1.992
After features/support/hooks.rb:331 0.969
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
1:35.242
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.039
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.018
And Tor is ready 20.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.136
Given I shutdown Tails and wait for the computer to power off 19.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 40.629
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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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:331 5.277 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:06:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6356/artifact/build-artifacts/01:06:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6356/artifact/build-artifacts/01:06:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6356/artifact/build-artifacts/01:06:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6356/artifact/build-artifacts/01:06:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
24.719
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.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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 16.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 1.052
After features/support/hooks.rb:100 0.000