Project Number Date
test_Tails_ISO_stable 6441 11 Jun 2026, 14:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 3 9 0 0 87 4 3 7 12:14.066 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.778
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.147
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.138
And I write an old version of the Tails USB image to disk "old" 14.631
When I start Tails from USB drive "old" with network unplugged 56.417
Then the boot device has safe access rights 2.730
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.799
After features/support/hooks.rb:108 0.018
Tags: @product
1:29.572
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.008
Steps
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 58.217
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 26.668
And I take note of which tps features are available 4.244
Python 
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1124:in `/^I take note of which tps features are available$/'
features/usb_upgrade.feature:39:in `And I take note of which tps features are available'
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 4.912 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:13:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:13:05_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:13:05_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:13:05_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:13:05_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.024
Tags: @product
1:17.009
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.018
Steps
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.828
Then Tails is running from USB drive "old" 0.321
And all tps features are active 5.398
When I write some files expected to persist 0.289
Python 
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1083:in `/^I write some files expected to persist$/'
features/usb_upgrade.feature:49:in `When I write some files expected to persist'
# 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 4.957 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:14:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:14:27_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:14:27_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/6441/artifact/build-artifacts/01:14:27_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/6441/artifact/build-artifacts/01:14:27_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.023
Tags: @product
2:16.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.054
And I log in to a new session 13.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.888
And I plug USB drive "to_upgrade" 2.339
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.837
Then the running Tails is installed on USB drive "to_upgrade" 17.813
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.120
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.111
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.023
Steps
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.856
Then all tps features from the old Tails version are active 1.227
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.573
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:1132:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 4.796 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:18:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:18:09_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:18:09_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6441/artifact/build-artifacts/01:18:09_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/6441/artifact/build-artifacts/01:18:09_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:14.776
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.357
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.021
And Tor is ready 14.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.422
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.177
Given I shutdown Tails and wait for the computer to power off 10.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.726
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.286
When the network is plugged 0.016
And Tor is ready 10.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.582
Given I shutdown Tails and wait for the computer to power off 4.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.978
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.031
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.017
And Tor is ready 10.042
Then the Upgrader considers the system as up-to-date 10.635
# 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.462
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.320
After features/support/hooks.rb:339 0.695
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
21.882
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.868
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.278
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.000