Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 11 24 Aug 2026, 13:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 59 1 27 0 0 87 6 1 7 8:32.721 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:17.266
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.216
When I start Tails from USB drive "old" with network unplugged 57.322
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 4.049
After features/support/hooks.rb:108 0.011
Tags: @product
1:28.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 51.508
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 24.474
And I take note of which tps features are available 7.413
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 4.203
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.006
Tags: @product
1:43.560
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.411
Then Tails is running from USB drive "old" 0.274
And all tps features are active 8.391
When I write some files expected to persist 0.998
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 1.777
And I take note of which tps features are available 9.191
And I shutdown Tails and wait for the computer to power off 2.713
# 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.256
After features/support/hooks.rb:339 0.381
After features/support/hooks.rb:108 0.017
Tags: @product
2:15.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.090
And I log in to a new session 12.243
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.935
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.074
Then the running Tails is installed on USB drive "to_upgrade" 19.305
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 3.583
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.956
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.254
Then all tps features from the old Tails version are active 1.230
And Tails is running from USB drive "to_upgrade" 0.174
And the boot device has safe access rights 2.210
And the expected persistent files created with the old Tails version are present in the filesystem 1.150
And all persistent directories from the old Tails version have safe access rights 1.866
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.063
Tags: @product @automatic_upgrade
21.549
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 5.149
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.172
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.026
And Tor is ready 15.505
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:718:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:672:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~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.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.965 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:16:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_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_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.000
Tags: @product @automatic_upgrade
15.677
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 4.925
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.917
After features/support/hooks.rb:339 0.993
After features/support/hooks.rb:108 0.000