Project Number Date
test_Tails_ISO_stable 5723 18 Jun 2025, 17:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 71 1 15 0 0 87 6 1 7 23:32.423 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:11.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 41.573
When I start Tails from USB drive "old" with network unplugged 2:17.671
Then the boot device has safe access rights 4.403
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.352
And udev-watchdog is monitoring the correct device 2.652
And I unplug USB drive "old" 3.059
After features/support/hooks.rb:330 5.695
After features/support/hooks.rb:100 0.016
Tags: @product
3:11.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.346
And I start Tails from USB drive "old" with network unplugged and I login 2:14.000
Then Tails is running from USB drive "old" 1.112
And I create a persistent partition 42.813
And I take note of which tps features are available 2.556
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 9.822
After features/support/hooks.rb:330 0.575
After features/support/hooks.rb:100 0.036
Tags: @product
4:35.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.425
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:42.122
Then Tails is running from USB drive "old" 0.621
And all tps features are active 3.443
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.802
And I take note of which tps features are available 0.665
And I shutdown Tails and wait for the computer to power off 11.116
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.482
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.011
Tags: @product
3:18.554
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 17.458
And I log in to a new session 28.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.875
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.016
Then the running Tails is installed on USB drive "to_upgrade" 32.265
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 6.452
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.103
Given a computer 1.382
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:57.894
Then all tps features from the old Tails version are active 5.095
And Tails is running from USB drive "to_upgrade" 1.050
And the boot device has safe access rights 3.688
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 3.328
After features/support/hooks.rb:330 3.142
After features/support/hooks.rb:100 0.364
Tags: @product @automatic_upgrade
5:0.616
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.128
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.032
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.127
And Tails is fooled to think it is running version 6.0~testoverlayfs 1.405
And the file system changes introduced in version 6.2~testoverlayfs are not present 3.713
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.603
When the network is plugged 0.157
And Tor is ready 28.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.043
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.983
Given I shutdown Tails and wait for the computer to power off 11.067
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.544
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 6.865
And the file system changes introduced in version 6.2~testoverlayfs are present 1.753
And only the 6.2~testoverlayfs SquashFS delta is installed 0.236
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.605
# 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.644
When the network is plugged 0.170
And Tor is ready 14.103
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:105:in `And Tor is ready'
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.530 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:33:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5723/artifact/build-artifacts/02:33:37_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_stable/5723/artifact/build-artifacts/02:33:37_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5723/artifact/build-artifacts/02:33:37_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5723/artifact/build-artifacts/02:33:37_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
1:0.949
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 with a persistent partition enabled and logged in 28.043
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 26.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.413
After features/support/hooks.rb:330 1.775
After features/support/hooks.rb:100 0.000