Project Number Date
test_Tails_ISO_21619-tor-browser-15.0.16 1 11 Jun 2026, 15:10

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:31.000 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:19.975
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 14.715
When I start Tails from USB drive "old" with network unplugged 1:0.368
Then the boot device has safe access rights 2.849
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 3.712
After features/support/hooks.rb:108 0.042
Tags: @product
1:33.984
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.015
Steps
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 59.176
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 29.436
And I take note of which tps features are available 4.886
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.006 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:15:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:15:39_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_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:15:39_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:15:39_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:15:39_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.016
Tags: @product
1:18.597
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.138
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.306
Then Tails is running from USB drive "old" 0.233
And all tps features are active 5.754
When I write some files expected to persist 0.165
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.861 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:17:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:17:02_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_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:17:02_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_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:17:02_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_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:17:02_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.019
Tags: @product
2:17.844
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 without a persistent partition and stopped at Tails Greeter's login screen 9.147
And I log in to a new session 14.891
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.493
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.841
Then the running Tails is installed on USB drive "to_upgrade" 16.804
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.138
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.632
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.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.596
Then all tps features from the old Tails version are active 1.093
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.467
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.800 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:20:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:20:45_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_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:20:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:20:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21619-tor-browser-15.0.16/1/artifact/build-artifacts/01:20:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
4:21.001
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 9.872
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
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.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.019
And Tor is ready 14.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.526
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.116
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.228
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
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.172
# 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.276
When the network is plugged 0.031
And Tor is ready 10.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.467
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.971
Given I shutdown Tails and wait for the computer to power off 4.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.354
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 6.892
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.014
And Tor is ready 10.653
Then the Upgrader considers the system as up-to-date 10.600
# 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.371
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:339 1.083
After features/support/hooks.rb:108 0.104
Tags: @product @automatic_upgrade
21.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.850
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.657
After features/support/hooks.rb:339 0.956
After features/support/hooks.rb:108 0.000