Project Number Date
test_Tails_ISO_stable 5769 15 Jul 2025, 19:50

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 50 2 35 0 0 87 5 2 7 24:47.779 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
3:54.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.085
Given a computer 1.503
And I create a 7200 MiB disk named "old" 0.246
And I plug USB drive "old" 1.375
And I write an old version of the Tails USB image to disk "old" 1:6.793
When I start Tails from USB drive "old" with network unplugged 2:39.515
Then the boot device has safe access rights 3.902
And Tails is running from USB drive "old" 0.523
And there is no persistence partition on USB drive "old" 0.135
And process "udev-watchdog" is running 0.138
And udev-watchdog is monitoring the correct device 0.408
And I unplug USB drive "old" 0.410
After features/support/hooks.rb:330 7.897
After features/support/hooks.rb:100 0.527
Tags: @product
4:5.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 1.617
And I start Tails from USB drive "old" with network unplugged and I login 2:44.545
Then Tails is running from USB drive "old" 0.621
And I create a persistent partition 1:0.131
And I take note of which tps features are available 2.939
Then a Tails persistence partition exists on USB drive "old" 1.198
And I shutdown Tails and wait for the computer to power off 14.745
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.021
Tags: @product
5:47.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:25.609
Then Tails is running from USB drive "old" 0.830
And all tps features are active 11.962
When I write some files expected to persist 2.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 3.012
And I take note of which tps features are available 0.614
And I shutdown Tails and wait for the computer to power off 13.438
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 48.537
After features/support/hooks.rb:330 5.167
After features/support/hooks.rb:100 0.174
Tags: @product
4:12.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.099
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.201
And I log in to a new session 41.346
And I clone USB drive "old" to a new USB drive "to_upgrade" 10.704
And I plug USB drive "to_upgrade" 3.046
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:12.657
Then the running Tails is installed on USB drive "to_upgrade" 47.934
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:330 7.579
After features/support/hooks.rb:100 0.000
Tags: @product
4:32.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.521
Given a computer 2.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:5.314
Then all tps features from the old Tails version are active 3.217
And Tails is running from USB drive "to_upgrade" 0.471
And the boot device has safe access rights 14.743
And the expected persistent files created with the old Tails version are present in the filesystem 1.837
And all persistent directories from the old Tails version have safe access rights 4.227
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
1:30.418
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:30.418
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 6.984 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:11:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:11:33_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:11:33_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:11:33_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:11:33_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
44.823
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.604
And the signing key used by the Upgrader is outdated 1.188
But a current signing key is available on our website 0.000
When the network is plugged 1.319
And Tor is ready 15.314
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 11.560 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:12:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:12:32_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:12:32_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:12:32_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5769/artifact/build-artifacts/02:12:32_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000