Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 1 20 Aug 2026, 15:05

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:31.723 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.612
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.022
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.678
When I start Tails from USB drive "old" with network unplugged 58.753
Then the boot device has safe access rights 2.430
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 1.225
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.182
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 49.425
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 24.615
And I take note of which tps features are available 9.139
Then a Tails persistence partition exists on USB drive "old" 0.683
And I shutdown Tails and wait for the computer to power off 3.986
After features/support/hooks.rb:339 0.195
After features/support/hooks.rb:108 0.006
Tags: @product
1:45.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.605
Then Tails is running from USB drive "old" 0.204
And all tps features are active 9.934
When I write some files expected to persist 1.288
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.969
And I take note of which tps features are available 6.678
And I shutdown Tails and wait for the computer to power off 2.555
# 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.497
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.975
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 without a persistent partition and stopped at Tails Greeter's login screen 5.817
And I log in to a new session 12.655
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.923
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.866
Then the running Tails is installed on USB drive "to_upgrade" 20.205
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 3.875
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.248
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.073
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.180
And the boot device has safe access rights 2.321
And the expected persistent files created with the old Tails version are present in the filesystem 0.925
And all persistent directories from the old Tails version have safe access rights 1.638
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
21.877
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.745
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
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.265
When the network is plugged 0.032
And Tor is ready 15.290
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:713:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:667: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 5.292 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:16:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_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/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/1/artifact/build-artifacts/01:16:13_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/1/artifact/build-artifacts/01:16:13_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.000
Tags: @product @automatic_upgrade
16.516
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.348
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.033
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.076
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.000