Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 9 09 Aug 2026, 16:35

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:58.641 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:5.628
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.044
When I start Tails from USB drive "old" with network unplugged 48.902
Then the boot device has safe access rights 1.962
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.304
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.352
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 47.541
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 22.352
And I take note of which tps features are available 5.664
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 3.947
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.637
Then Tails is running from USB drive "old" 0.202
And all tps features are active 6.822
When I write some files expected to persist 1.051
# 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.200
And all persistent directories from the old Tails version have safe access rights 1.444
And I take note of which tps features are available 5.647
And I shutdown Tails and wait for the computer to power off 2.499
# 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.205
After features/support/hooks.rb:339 0.282
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.032
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.096
And I log in to a new session 11.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.549
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.491
Then the running Tails is installed on USB drive "to_upgrade" 17.442
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 2.204
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.237
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.616
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 2.081
And the expected persistent files created with the old Tails version are present in the filesystem 0.936
And all persistent directories from the old Tails version have safe access rights 1.356
After features/support/hooks.rb:339 0.944
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:28.067
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 7.880
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
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.148
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.029
And Tor is ready 12.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.647
Given I shutdown Tails and wait for the computer to power off 5.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.611
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.591
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.186
When the network is plugged 0.059
And Tor is ready 10.261
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.294
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.380
Given I shutdown Tails and wait for the computer to power off 3.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.003
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 4.991 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:12:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.339
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.665
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 8.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.009
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.000