Project Number Date
test_Tails_ISO_tps-restart-gnome-software 2 11 Jun 2026, 13:39

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:12.286 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:26.185
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.615
When I start Tails from USB drive "old" with network unplugged 1:6.632
Then the boot device has safe access rights 2.727
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:339 1.791
After features/support/hooks.rb:108 0.021
Tags: @product
1:28.823
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.026
Steps
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 58.742
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 25.296
And I take note of which tps features are available 4.316
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 5.149 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:12:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.031
Tags: @product
1:16.930
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.038
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.227
Then Tails is running from USB drive "old" 0.326
And all tps features are active 5.064
When I write some files expected to persist 0.130
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.029 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:13:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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:15.996
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.954
And I log in to a new session 14.281
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.003
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.923
Then the running Tails is installed on USB drive "to_upgrade" 16.323
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:339 2.768
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.570
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.019
Steps
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.496
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.562
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:17:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:7.551
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.543
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.019
And Tor is ready 13.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.190
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.905
Given I shutdown Tails and wait for the computer to power off 9.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.854
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.189
When the network is plugged 0.018
And Tor is ready 11.246
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.051
Given I shutdown Tails and wait for the computer to power off 3.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.738
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.340
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.020
And Tor is ready 11.350
Then the Upgrader considers the system as up-to-date 10.758
# 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.573
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:339 1.002
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
21.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.017
And Tor is ready 10.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.270
After features/support/hooks.rb:339 0.975
After features/support/hooks.rb:108 0.000