Project Number Date
test_Tails_ISO_devel 4514 26 Jul 2026, 11:26

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:43.666 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:6.034
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.606
When I start Tails from USB drive "old" with network unplugged 48.235
Then the boot device has safe access rights 2.412
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.397
After features/support/hooks.rb:108 0.007
Tags: @product
3:1.175
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.002
Steps
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 3:1.087
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: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.565 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:09:00)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:09:00_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:09:00_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:09:00_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.052
Tags: @product
3:1.037
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.001
Steps
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:0.993
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: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.709 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:12:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:12:12_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_devel/4514/artifact/build-artifacts/01:12:12_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_devel/4514/artifact/build-artifacts/01:12:12_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.051
Tags: @product
2:12.964
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 without a persistent partition and stopped at Tails Greeter's login screen 8.147
And I log in to a new session 13.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.109
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.885
Then the running Tails is installed on USB drive "to_upgrade" 15.468
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.116
After features/support/hooks.rb:108 0.000
Tags: @product
3:1.024
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.003
Steps
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.961
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.806 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:17:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:17:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:17:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4514/artifact/build-artifacts/01:17:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.053
Tags: @product @automatic_upgrade
3:59.469
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.272
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.016
And Tor is ready 13.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.283
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.765
Given I shutdown Tails and wait for the computer to power off 8.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.310
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.616
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.213
When the network is plugged 0.013
And Tor is ready 10.060
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.908
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.565
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.669
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.015
And Tor is ready 10.392
Then the Upgrader considers the system as up-to-date 10.777
# 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 4.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
21.960
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 7.756
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.098
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.576
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.000