Project Number Date
test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring 15 23 Aug 2026, 10:48

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 26:10.640 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:9.629
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.375
When I start Tails from USB drive "old" with network unplugged 52.303
Then the boot device has safe access rights 2.145
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.453
After features/support/hooks.rb:108 0.038
Tags: @product
1:19.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 46.899
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 23.080
And I take note of which tps features are available 6.095
Then a Tails persistence partition exists on USB drive "old" 0.502
And I shutdown Tails and wait for the computer to power off 2.605
After features/support/hooks.rb:339 0.397
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.927
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.567
Then Tails is running from USB drive "old" 0.246
And all tps features are active 6.713
When I write some files expected to persist 0.899
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.428
And I take note of which tps features are available 6.047
And I shutdown Tails and wait for the computer to power off 2.551
# 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.017
After features/support/hooks.rb:339 0.343
After features/support/hooks.rb:108 0.005
Tags: @product
15:29.889
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.181
And I log in to a new session 11.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.577
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 15:7.835
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.105 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:30:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/15/artifact/build-artifacts/02:30:43_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/15/artifact/build-artifacts/02:30:43_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/15/artifact/build-artifacts/02:30:43_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/15/artifact/build-artifacts/02:30:43_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:108 0.000
Tags: @product
3:0.908
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.001
Steps
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.837
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.787 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:33:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/15/artifact/build-artifacts/02:33:49_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/15/artifact/build-artifacts/02:33:49_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/15/artifact/build-artifacts/02:33:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
3:24.085
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 8.017
And no SquashFS delta is installed 0.084
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.255
When the network is plugged 0.033
And Tor is ready 12.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.127
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.104
Given I shutdown Tails and wait for the computer to power off 5.251
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.462
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.510
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.159
When the network is plugged 0.034
And Tor is ready 9.888
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.460
Given I shutdown Tails and wait for the computer to power off 4.034
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.706
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.542
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.151
When the network is plugged 0.032
And Tor is ready 10.026
Then the Upgrader considers the system as up-to-date 0.090
# 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.081
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.669
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
19.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.713
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.032
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.986
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.000