Project Number Date
test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring 5 12 Aug 2026, 11:00

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 77 2 8 0 0 87 5 2 7 27:31.216 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:15.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.517
When I start Tails from USB drive "old" with network unplugged 58.196
Then the boot device has safe access rights 2.131
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.496
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.074
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 49.185
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 23.544
And I take note of which tps features are available 6.373
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 4.099
After features/support/hooks.rb:339 0.290
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.360
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 with persistence enabled 1:2.886
Then Tails is running from USB drive "old" 0.226
And all tps features are active 8.525
When I write some files expected to persist 1.325
# 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.212
And all persistent directories from the old Tails version have safe access rights 1.898
And I take note of which tps features are available 6.058
And I shutdown Tails and wait for the computer to power off 2.545
# 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.436
After features/support/hooks.rb:339 0.444
After features/support/hooks.rb:108 0.005
Tags: @product
15:32.106
Scenario Upgrading an old Tails USB installation from another Tails USB drive
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 without a persistent partition and stopped at Tails Greeter's login screen 8.557
And I log in to a new session 12.946
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.665
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 15:7.737
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [application | ]: child with name='Information' roleName='alert'
STDOUT:

STDERR:


./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/usb.rb:271:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:269:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:269:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:339 5.593 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:27:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:27:50_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:27:50_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:27:50_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:27:50_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:108 0.000
Tags: @product
3:0.985
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.896
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuSyslinux.png", "TailsBootMenuSyslinux_alt.png"] on the screen
./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:357:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:354:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:406:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:238:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:354:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:406: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 10.836 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:30:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:30:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:30:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/5/artifact/build-artifacts/02:30:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.055
Tags: @product @automatic_upgrade
4:9.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 21.579
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.039
And Tor is ready 14.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.543
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.805
Given I shutdown Tails and wait for the computer to power off 5.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.110
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.594
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.089
# 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.205
When the network is plugged 0.025
And Tor is ready 20.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.471
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.166
Given I shutdown Tails and wait for the computer to power off 3.957
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.131
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.023
And Tor is ready 20.808
Then the Upgrader considers the system as up-to-date 0.095
# 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 3.624
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:339 1.020
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
33.759
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 21.669
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.257
After features/support/hooks.rb:339 0.943
After features/support/hooks.rb:108 0.000