Project Number Date
test_Tails_ISO_21019-fix-custom-package-versioning-scheme 2 18 Jun 2025, 16:38

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 59 2 26 0 0 87 5 2 7 1:5:34.694 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:41.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 40.421
When I start Tails from USB drive "old" with network unplugged 2:55.634
Then the boot device has safe access rights 3.330
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.291
After features/support/hooks.rb:330 3.593
After features/support/hooks.rb:100 0.007
Tags: @product
4:0.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 2:58.869
Then Tails is running from USB drive "old" 1.013
And I create a persistent partition 39.799
And I take note of which tps features are available 4.917
Then a Tails persistence partition exists on USB drive "old" 1.571
And I shutdown Tails and wait for the computer to power off 13.790
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.006
Tags: @product
4:56.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:5.481
Then Tails is running from USB drive "old" 1.314
And all tps features are active 2.741
When I write some files expected to persist 2.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.959
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 10.686
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.438
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.980
And I log in to a new session 32.646
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.975
And I plug USB drive "to_upgrade" 5.771
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.028
Then the running Tails is installed on USB drive "to_upgrade" 31.500
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 3.540
After features/support/hooks.rb:100 0.000
Tags: @product
3:46.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:31.310
Then all tps features from the old Tails version are active 2.509
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 4.136
And the expected persistent files created with the old Tails version are present in the filesystem 1.894
And all persistent directories from the old Tails version have safe access rights 6.203
After features/support/hooks.rb:330 1.457
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
22:58.179
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.637
And no SquashFS delta is installed 1.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.872
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.230
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.427
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.567
When the network is plugged 0.073
And Tor is ready 24.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:14.436
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
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.120 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:01:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:01:29_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_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
22:53.005
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.437
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.787
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.113
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 25.236
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:14.254
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.944 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:24:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:24:28_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:24:28_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:24:28_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:24:28_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000