Project Number Date
test_Tails_ISO_devel 4443 11 Jun 2026, 15:00

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:9.795 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:3.344
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.042
Given a computer 0.256
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.078
And I write an old version of the Tails USB image to disk "old" 14.518
When I start Tails from USB drive "old" with network unplugged 43.358
Then the boot device has safe access rights 3.265
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:339 3.813
After features/support/hooks.rb:108 0.023
Tags: @product
1:27.651
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.023
Steps
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 57.465
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.412
And I take note of which tps features are available 4.332
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.948 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:14:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_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_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.024
Tags: @product
1:17.585
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.019
Steps
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.465
Then Tails is running from USB drive "old" 0.298
And all tps features are active 5.463
When I write some files expected to persist 0.149
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 5.025 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:16:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:16:10_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_devel/4443/artifact/build-artifacts/01:16:10_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/4443/artifact/build-artifacts/01:16:10_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/4443/artifact/build-artifacts/01:16:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.057
Tags: @product
2:18.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.184
And I log in to a new session 14.465
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.106
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.995
Then the running Tails is installed on USB drive "to_upgrade" 17.876
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:339 2.312
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.470
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.020
Steps
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.241
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.623
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.938 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:19:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_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_devel/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_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/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
4:20.801
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.890
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.026
And Tor is ready 13.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.198
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.827
Given I shutdown Tails and wait for the computer to power off 10.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.367
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.639
And the file system changes introduced in version 6.2~testoverlayfs are present 0.403
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.290
When the network is plugged 0.026
And Tor is ready 12.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.150
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.001
Given I shutdown Tails and wait for the computer to power off 7.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.765
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 6.447
And the file system changes introduced in version 6.3~testoverlayfs are present 0.413
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.018
And Tor is ready 10.132
Then the Upgrader considers the system as up-to-date 10.574
# 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.919
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
22.722
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.706
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.098
After features/support/hooks.rb:339 1.088
After features/support/hooks.rb:108 0.000