Project Number Date
test_Tails_ISO_devel 3880 23 Jun 2025, 12:03

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 44 2 41 0 0 87 5 2 7 26:18.406 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
4:44.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.388
And I create a 7200 MiB disk named "old" 0.096
And I plug USB drive "old" 1.082
And I write an old version of the Tails USB image to disk "old" 1:6.207
When I start Tails from USB drive "old" with network unplugged 3:22.921
Then the boot device has safe access rights 11.868
And Tails is running from USB drive "old" 0.445
And there is no persistence partition on USB drive "old" 0.130
And process "udev-watchdog" is running 0.176
And udev-watchdog is monitoring the correct device 0.601
And I unplug USB drive "old" 0.623
After features/support/hooks.rb:330 6.050
After features/support/hooks.rb:100 0.359
Tags: @product
4:29.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Given a computer 1.503
And I start Tails from USB drive "old" with network unplugged and I login 2:54.530
Then Tails is running from USB drive "old" 0.525
And I create a persistent partition 1:14.023
And I take note of which tps features are available 2.767
Then a Tails persistence partition exists on USB drive "old" 1.048
And I shutdown Tails and wait for the computer to power off 15.340
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.016
Tags: @product
5:45.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:17.872
Then Tails is running from USB drive "old" 1.141
And all tps features are active 2.092
When I write some files expected to persist 2.760
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.475
And all persistence configuration files have safe access rights 0.550
And all persistent directories from the old Tails version have safe access rights 13.911
And I take note of which tps features are available 0.587
And I shutdown Tails and wait for the computer to power off 10.099
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 55.646
After features/support/hooks.rb:330 0.504
After features/support/hooks.rb:100 0.013
Tags: @product
4:16.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 19.694
And I log in to a new session 39.407
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.516
And I plug USB drive "to_upgrade" 7.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:16.288
Then the running Tails is installed on USB drive "to_upgrade" 44.685
And I unplug USB drive "to_upgrade" 0.424
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:330 3.699
After features/support/hooks.rb:100 0.000
Tags: @product
4:17.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:54.622
Then all tps features from the old Tails version are active 2.600
And Tails is running from USB drive "to_upgrade" 0.705
And the boot device has safe access rights 14.314
And the expected persistent files created with the old Tails version are present in the filesystem 1.965
And all persistent directories from the old Tails version have safe access rights 3.533
After features/support/hooks.rb:330 1.873
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
1:27.036
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:27.036
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
Hooks
After features/support/hooks.rb:330 5.885
Error message 
execution expired (RemoteShell::Timeout)
./features/support/hooks.rb:339:in `sleep'
./features/support/hooks.rb:339:in `After'
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:16.977
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 1:16.977
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:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
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 signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 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
After features/support/hooks.rb:330 6.785 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:27:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3880/artifact/build-artifacts/02:27:07_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3880/artifact/build-artifacts/02:27:07_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3880/artifact/build-artifacts/02:27:07_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3880/artifact/build-artifacts/02:27:07_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000