Project Number Date
test_Tails_ISO_devel 3882 24 Jun 2025, 12:43

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 25:18.688 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:19.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.356
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:4.545
When I start Tails from USB drive "old" with network unplugged 2:6.916
Then the boot device has safe access rights 4.495
And Tails is running from USB drive "old" 0.599
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.137
And udev-watchdog is monitoring the correct device 0.525
And I unplug USB drive "old" 0.264
After features/support/hooks.rb:330 7.637
After features/support/hooks.rb:100 0.592
Tags: @product
4:14.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.322
Given a computer 0.954
And I start Tails from USB drive "old" with network unplugged and I login 2:46.932
Then Tails is running from USB drive "old" 0.523
And I create a persistent partition 1:4.042
And I take note of which tps features are available 7.191
Then a Tails persistence partition exists on USB drive "old" 5.431
And I shutdown Tails and wait for the computer to power off 9.068
After features/support/hooks.rb:330 6.391
After features/support/hooks.rb:100 0.346
Tags: @product
6:9.889
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.137
Given a computer 0.752
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:41.127
Then Tails is running from USB drive "old" 2.296
And all tps features are active 2.654
When I write some files expected to persist 2.782
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.548
And all persistence configuration files have safe access rights 0.649
And all persistent directories from the old Tails version have safe access rights 13.587
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 6.775
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 58.190
After features/support/hooks.rb:330 0.233
After features/support/hooks.rb:100 0.017
Tags: @product
4:35.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.478
And I log in to a new session 39.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.268
And I plug USB drive "to_upgrade" 12.001
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:19.759
Then the running Tails is installed on USB drive "to_upgrade" 59.582
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.000
Tags: @product
4:31.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.297
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:59.935
Then all tps features from the old Tails version are active 4.325
And Tails is running from USB drive "to_upgrade" 6.561
And the boot device has safe access rights 6.808
And the expected persistent files created with the old Tails version are present in the filesystem 2.090
And all persistent directories from the old Tails version have safe access rights 11.392
After features/support/hooks.rb:330 3.342
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
1:16.033
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.012
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.033
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 7.067 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:55:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:55:55_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_devel/3882/artifact/build-artifacts/02:55:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:55:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:55:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:12.684
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.684
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.917 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:57:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:57:15_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/3882/artifact/build-artifacts/02:57:15_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:57:15_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3882/artifact/build-artifacts/02:57:15_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000