Project Number Date
test_Tails_ISO_stable 6495 10 Jul 2026, 11:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 80 1 6 0 0 87 6 1 7 11:37.701 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.180
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.287
When I start Tails from USB drive "old" with network unplugged 45.816
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:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:339 4.842 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:04:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6495/artifact/build-artifacts/01:04:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6495/artifact/build-artifacts/01:04:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6495/artifact/build-artifacts/01:04:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6495/artifact/build-artifacts/01:04:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.267
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.892
And I take note of which tps features are available 3.755
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 8.250
After features/support/hooks.rb:339 0.417
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.102
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.979
Then Tails is running from USB drive "old" 0.269
And all tps features are active 4.697
When I write some files expected to persist 1.171
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.298
And all persistent directories from the old Tails version have safe access rights 1.771
And I take note of which tps features are available 3.846
And I shutdown Tails and wait for the computer to power off 7.960
# 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.893
After features/support/hooks.rb:339 0.259
After features/support/hooks.rb:108 0.007
Tags: @product
2:7.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.883
And I log in to a new session 11.799
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.714
Then the running Tails is installed on USB drive "to_upgrade" 14.218
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 1.793
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.997
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.032
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.314
And all persistent directories from the old Tails version have safe access rights 1.919
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:53.185
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.164
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.013
And Tor is ready 13.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.539
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.172
Given I shutdown Tails and wait for the computer to power off 10.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.061
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.059
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.175
When the network is plugged 0.019
And Tor is ready 10.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.177
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.792
Given I shutdown Tails and wait for the computer to power off 8.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.249
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.016
And Tor is ready 10.575
Then the Upgrader considers the system as up-to-date 10.537
# 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.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.380
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.322
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.080
After features/support/hooks.rb:339 0.803
After features/support/hooks.rb:108 0.000