Project Number Date
test_Tails_ISO_devel 3888 26 Jun 2025, 18:12

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 18:37.352 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:21.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.202
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" 32.857
When I start Tails from USB drive "old" with network unplugged 1:41.869
Then the boot device has safe access rights 3.901
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.914
After features/support/hooks.rb:330 6.522
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:37.456
Then Tails is running from USB drive "old" 0.455
And I create a persistent partition 34.270
And I take note of which tps features are available 3.001
Then a Tails persistence partition exists on USB drive "old" 1.150
And I shutdown Tails and wait for the computer to power off 7.051
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.467
Then Tails is running from USB drive "old" 0.701
And all tps features are active 2.833
When I write some files expected to persist 2.320
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.670
And all persistent directories from the old Tails version have safe access rights 2.434
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 6.696
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.697
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.278
And I log in to a new session 22.978
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.568
And I plug USB drive "to_upgrade" 2.691
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.358
Then the running Tails is installed on USB drive "to_upgrade" 31.234
And I unplug USB drive "to_upgrade" 0.258
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:330 2.814
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.241
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.079
Given a computer 0.455
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.816
Then all tps features from the old Tails version are active 1.894
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 4.340
And the expected persistent files created with the old Tails version are present in the filesystem 1.533
And all persistent directories from the old Tails version have safe access rights 2.883
After features/support/hooks.rb:330 1.251
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:26.120
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.547
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.377
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.069
And Tor is ready 24.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.122
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.391
Given I shutdown Tails and wait for the computer to power off 12.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.766
Then Tails is running version 6.2~testoverlayfs 0.046
And all tps features are active 4.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.689
And only the 6.2~testoverlayfs SquashFS delta is installed 0.143
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.612
# 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.520
When the network is plugged 0.204
And Tor is ready 14.859
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 5.119 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:01:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3888/artifact/build-artifacts/02:01:05_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/3888/artifact/build-artifacts/02:01:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3888/artifact/build-artifacts/02:01:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3888/artifact/build-artifacts/02:01:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
43.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.428
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.798
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.094
But a current signing key is available on our website 0.000
When the network is plugged 0.128
And Tor is ready 21.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.880
After features/support/hooks.rb:330 1.654
After features/support/hooks.rb:100 0.000