Project Number Date
test_Tails_ISO_devel 3812 15 May 2025, 09:49

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 16:0.478 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
2:13.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 35.849
When I start Tails from USB drive "old" with network unplugged 1:32.303
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 7.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:29.269
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 32.658
And I take note of which tps features are available 1.765
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.407
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.859
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.649
When I write some files expected to persist 1.863
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.527
And I shutdown Tails and wait for the computer to power off 4.412
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.806
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.022
Tags: @product
2:51.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.373
And I log in to a new session 18.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.945
Then the running Tails is installed on USB drive "to_upgrade" 23.018
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 6.728
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.957
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.831
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.570
After features/support/hooks.rb:330 1.104
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
1:44.158
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.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:44.158
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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.377 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:46:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_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/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:23.999
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.999
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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.335 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:48:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_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/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000