Project Number Date
test_Tails_ISO_stable 5966 24 Nov 2025, 12:43

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 20:48.687 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
2:16.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.910
When I start Tails from USB drive "old" with network unplugged 1:38.940
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 3.983
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.692
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 3:1.512
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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:331 10.738 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:30:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.096
Tags: @product
3:1.569
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:1.388
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:331 10.858 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:34:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:34:07_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_stable/5966/artifact/build-artifacts/01:34:07_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_stable/5966/artifact/build-artifacts/01:34:07_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.111
Tags: @product
2:58.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.044
And I log in to a new session 18.410
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.181
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.822
Then the running Tails is installed on USB drive "to_upgrade" 25.569
And I unplug USB drive "to_upgrade" 0.667
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:331 3.705
After features/support/hooks.rb:100 0.000
Tags: @product
3:1.568
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.156
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:1.411
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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:331 10.927 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:40:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.138
Tags: @product @automatic_upgrade
5:35.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.997
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 1.287
And Tor is ready 16.838
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.231
Given I shutdown Tails and wait for the computer to power off 12.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.535
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.653
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.250
When the network is plugged 0.055
And Tor is ready 11.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.314
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.061
Given I shutdown Tails and wait for the computer to power off 4.756
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.477
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 1.739
And Tor is ready 16.542
Then the Upgrader considers the system as up-to-date 0.225
# 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 5.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.664
After features/support/hooks.rb:331 0.976
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
54.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 41.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
After features/support/hooks.rb:331 0.730
After features/support/hooks.rb:100 0.000