Project Number Date
test_Tails_ISO_stable 6573 11 Aug 2026, 11:57

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:18.072 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:0.364
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.122
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.921
When I start Tails from USB drive "old" with network unplugged 42.634
Then the boot device has safe access rights 2.083
And Tails is running from USB drive "old" 0.184
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.773
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 49.615
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 23.671
And I take note of which tps features are available 6.381
Then a Tails persistence partition exists on USB drive "old" 0.449
And I shutdown Tails and wait for the computer to power off 4.045
After features/support/hooks.rb:339 0.403
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.573
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.647
Then Tails is running from USB drive "old" 0.197
And all tps features are active 6.887
When I write some files expected to persist 1.165
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 1.700
And I take note of which tps features are available 6.874
And I shutdown Tails and wait for the computer to power off 4.279
# 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.199
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.005
Tags: @product
2:27.978
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 22.163
And I log in to a new session 11.751
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.593
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.734
Then the running Tails is installed on USB drive "to_upgrade" 19.235
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 1.499
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.610
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.132
And the expected persistent files created with the old Tails version are present in the filesystem 0.959
And all persistent directories from the old Tails version have safe access rights 1.715
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
1:15.129
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.585
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.024
And Tor is ready 12.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.479
Given I shutdown Tails and wait for the computer to power off 5.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 41.216
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238: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:339 4.786 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:17:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6573/artifact/build-artifacts/01:17:58_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/6573/artifact/build-artifacts/01:17:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6573/artifact/build-artifacts/01:17:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6573/artifact/build-artifacts/01:17:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
25.830
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 with a persistent partition enabled and logged in 8.418
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
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.076
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 14.934
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.057
After features/support/hooks.rb:339 0.875
After features/support/hooks.rb:108 0.000