Project Number Date
test_Tails_ISO_ignore-private-backports 4 09 Jul 2025, 07:24

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:18:49.973 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
5:56.901
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 1:13.934
When I start Tails from USB drive "old" with network unplugged 4:29.718
Then the boot device has safe access rights 10.773
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.393
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 7.736
After features/support/hooks.rb:100 0.181
Tags: @product
6:12.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.101
Given a computer 2.532
And I start Tails from USB drive "old" with network unplugged and I login 4:30.015
Then Tails is running from USB drive "old" 1.138
And I create a persistent partition 1:16.684
And I take note of which tps features are available 4.252
Then a Tails persistence partition exists on USB drive "old" 1.186
And I shutdown Tails and wait for the computer to power off 17.168
After features/support/hooks.rb:330 0.322
After features/support/hooks.rb:100 0.009
Tags: @product
8:0.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 6:38.054
Then Tails is running from USB drive "old" 1.474
And all tps features are active 3.778
When I write some files expected to persist 11.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.405
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 3.328
And I take note of which tps features are available 0.668
And I shutdown Tails and wait for the computer to power off 15.878
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 44.784
After features/support/hooks.rb:330 0.289
After features/support/hooks.rb:100 0.076
Tags: @product
4:40.602
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 20.568
And I log in to a new session 59.646
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.775
And I plug USB drive "to_upgrade" 6.938
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:15.911
Then the running Tails is installed on USB drive "to_upgrade" 47.302
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 3.681
After features/support/hooks.rb:100 0.000
Tags: @product
5:49.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.163
Given a computer 1.389
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 5:22.969
Then all tps features from the old Tails version are active 5.589
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 4.433
And the expected persistent files created with the old Tails version are present in the filesystem 1.815
And all persistent directories from the old Tails version have safe access rights 13.227
After features/support/hooks.rb:330 0.877
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
23:40.160
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.920
And no SquashFS delta is installed 0.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.080
And Tor is ready 36.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:38.199
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 12.245 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:15:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_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_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
24:29.407
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.187
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.513
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.220
And Tor is ready 25.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:38.908
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 10.552 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:40:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000