Project Number Date
test_Tails_ISO_stable 6579 14 Aug 2026, 07:18

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 10:57.261 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:16.537
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.125
When I start Tails from USB drive "old" with network unplugged 59.797
Then the boot device has safe access rights 1.889
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.151
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.551
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 46.805
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 22.538
And I take note of which tps features are available 5.722
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 2.536
After features/support/hooks.rb:339 0.451
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.065
Then Tails is running from USB drive "old" 0.173
And all tps features are active 6.334
When I write some files expected to persist 1.185
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.584
And I take note of which tps features are available 5.905
And I shutdown Tails and wait for the computer to power off 2.570
# 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.080
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.717
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 8.208
And I log in to a new session 12.034
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.602
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.582
Then the running Tails is installed on USB drive "to_upgrade" 16.822
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.102
After features/support/hooks.rb:339 1.569
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.620
Then all tps features from the old Tails version are active 0.878
And Tails is running from USB drive "to_upgrade" 0.182
And the boot device has safe access rights 2.053
And the expected persistent files created with the old Tails version are present in the filesystem 0.832
And all persistent directories from the old Tails version have safe access rights 1.418
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:22.830
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.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.073
And no SquashFS delta is installed 0.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.033
And Tor is ready 11.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.353
Given I shutdown Tails and wait for the computer to power off 5.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.928
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.510
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.167
When the network is plugged 0.042
And Tor is ready 9.997
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.858
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.863
Given I shutdown Tails and wait for the computer to power off 2.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.081
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446: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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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 5.153 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:13:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6579/artifact/build-artifacts/01:13:14_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/6579/artifact/build-artifacts/01:13:14_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6579/artifact/build-artifacts/01:13:14_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6579/artifact/build-artifacts/01:13:14_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.349
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.768
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.000