Project Number Date
test_Tails_ISO_devel 3894 02 Jul 2025, 14:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 59 1 27 0 0 87 6 1 7 24:10.833 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:39.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 3.985
And I create a 7200 MiB disk named "old" 0.730
And I plug USB drive "old" 1.570
And I write an old version of the Tails USB image to disk "old" 1:8.337
When I start Tails from USB drive "old" with network unplugged 2:19.417
Then the boot device has safe access rights 4.439
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 5.971
After features/support/hooks.rb:100 0.105
Tags: @product
4:4.971
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.068
Given a computer 1.287
And I start Tails from USB drive "old" with network unplugged and I login 2:30.153
Then Tails is running from USB drive "old" 1.172
And I create a persistent partition 1:6.102
And I take note of which tps features are available 7.489
Then a Tails persistence partition exists on USB drive "old" 1.234
And I shutdown Tails and wait for the computer to power off 17.531
After features/support/hooks.rb:330 0.466
After features/support/hooks.rb:100 0.032
Tags: @product
5:22.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:56.138
Then Tails is running from USB drive "old" 3.831
And all tps features are active 2.433
When I write some files expected to persist 2.239
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.325
And all persistence configuration files have safe access rights 0.597
And all persistent directories from the old Tails version have safe access rights 3.035
And I take note of which tps features are available 2.819
And I shutdown Tails and wait for the computer to power off 11.802
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 59.285
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
4:45.147
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 49.875
And I log in to a new session 38.190
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.364
And I plug USB drive "to_upgrade" 2.933
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:13.797
Then the running Tails is installed on USB drive "to_upgrade" 48.500
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:330 7.397
After features/support/hooks.rb:100 0.000
Tags: @product
4:24.838
Before features/support/hooks.rb:266 0.004
Before features/support/hooks.rb:273 0.183
Given a computer 1.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:56.554
Then all tps features from the old Tails version are active 6.543
And Tails is running from USB drive "to_upgrade" 0.500
And the boot device has safe access rights 4.039
And the expected persistent files created with the old Tails version are present in the filesystem 2.837
And all persistent directories from the old Tails version have safe access rights 13.319
After features/support/hooks.rb:330 2.122
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
49.259
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 24.242
And no SquashFS delta is installed 0.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.207
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 4.617
When the network is plugged 0.382
And Tor is ready 17.938
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:89:in `And Tor is ready'
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.745 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:20:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3894/artifact/build-artifacts/02:20:41_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/3894/artifact/build-artifacts/02:20:41_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3894/artifact/build-artifacts/02:20:41_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3894/artifact/build-artifacts/02:20:41_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:4.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.144
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 32.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.039
After features/support/hooks.rb:330 5.363
After features/support/hooks.rb:100 0.000