Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 23 09 Jun 2026, 20:01

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 11:48.453 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:12.682
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 14.060
When I start Tails from USB drive "old" with network unplugged 53.997
Then the boot device has safe access rights 2.795
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 1.906
After features/support/hooks.rb:104 0.036
Tags: @product
1:31.715
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 57.284
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 26.181
And I take note of which tps features are available 0.392
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 6.918
After features/support/hooks.rb:335 0.143
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.331
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.040
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.057
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.286
And all persistent directories from the old Tails version have safe access rights 2.075
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 8.629
# 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" 12.892
After features/support/hooks.rb:335 0.495
After features/support/hooks.rb:104 0.007
Tags: @product
2:16.075
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 9.029
And I log in to a new session 14.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.899
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.379
Then the running Tails is installed on USB drive "to_upgrade" 16.528
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:335 2.742
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.345
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.665
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.815
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.212
After features/support/hooks.rb:335 0.994
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:38.972
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.751
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.016
And Tor is ready 13.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.799
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.166
Given I shutdown Tails and wait for the computer to power off 6.931
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.877
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.302
When the network is plugged 0.021
And Tor is ready 10.463
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.907
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.740
Given I shutdown Tails and wait for the computer to power off 4.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.911
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:444: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: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:335 5.339 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:09:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/23/artifact/build-artifacts/01:09:55_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_21373-poweroff-inhibit/23/artifact/build-artifacts/01:09:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/23/artifact/build-artifacts/01:09:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/23/artifact/build-artifacts/01:09:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:104 0.028
Tags: @product @automatic_upgrade
21.331
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.669
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.614
After features/support/hooks.rb:335 0.897
After features/support/hooks.rb:104 0.000