Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 25 11 Jun 2026, 20:03

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 65 3 19 0 0 87 4 3 7 16:42.170 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:14.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.147
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 12.923
When I start Tails from USB drive "old" with network unplugged 57.420
Then the boot device has safe access rights 2.656
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.457
After features/support/hooks.rb:108 0.017
Tags: @product
3:1.129
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Steps
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login 3:1.015
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:354: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:235: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235: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:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:339 10.676 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:07:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:07:12_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:07:12_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:07:12_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.153
Tags: @product
3:0.963
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Steps
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:0.861
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:354: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:235: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# 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" 0.000
After features/support/hooks.rb:339 10.827 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:10:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:10:24_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:10:24_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:10:24_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.210
Tags: @product
2:10.610
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 without a persistent partition and stopped at Tails Greeter's login screen 8.098
And I log in to a new session 13.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.833
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.682
Then the running Tails is installed on USB drive "to_upgrade" 15.204
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 2.373
After features/support/hooks.rb:108 0.000
Tags: @product
3:1.005
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.030
Steps
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.899
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:354: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:235: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:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235: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.763 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:15:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:15:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/25/artifact/build-artifacts/01:15: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_21373-poweroff-inhibit/25/artifact/build-artifacts/01:15:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.153
Tags: @product @automatic_upgrade
3:52.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.229
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.346
When the network is plugged 0.019
And Tor is ready 12.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.426
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.100
Given I shutdown Tails and wait for the computer to power off 5.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.084
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.980
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.216
When the network is plugged 0.015
And Tor is ready 10.540
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.784
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.823
Given I shutdown Tails and wait for the computer to power off 4.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.499
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.436
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.014
And Tor is ready 9.959
Then the Upgrader considers the system as up-to-date 10.465
# 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.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.557
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.883
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.746
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.000