Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 58 11 Jun 2026, 14:57

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 11:45.278 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.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.119
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.954
When I start Tails from USB drive "old" with network unplugged 57.478
Then the boot device has safe access rights 2.604
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.743
After features/support/hooks.rb:108 0.051
Tags: @product
1:28.553
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.003
Steps
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 57.641
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 26.544
And I take note of which tps features are available 4.106
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.902 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:06:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_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_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.007
Tags: @product
1:10.964
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.004
Steps
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.462
Then Tails is running from USB drive "old" 0.321
And all tps features are active 4.942
When I write some files expected to persist 0.146
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.893 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:08:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_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_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_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_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_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_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.807
And I log in to a new session 14.108
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.968
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.062
Then the running Tails is installed on USB drive "to_upgrade" 15.893
And I unplug USB drive "to_upgrade" 0.173
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.179
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.168
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.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.289
Then all tps features from the old Tails version are active 1.033
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.514
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.666 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:11:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_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_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:4.202
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 7.828
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.016
And Tor is ready 13.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.092
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.382
Given I shutdown Tails and wait for the computer to power off 9.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.506
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 5.284
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.184
When the network is plugged 0.018
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.732
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.461
Given I shutdown Tails and wait for the computer to power off 8.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.251
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.012
And Tor is ready 11.996
Then the Upgrader considers the system as up-to-date 10.595
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.677
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
22.130
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.726
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.134
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.000