Project Number Date
test_Tails_ISO_devel 4127 18 Dec 2025, 08:38

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 16:6.302 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:3.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 6.754
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.404
When I start Tails from USB drive "old" with network unplugged 1:18.058
Then the boot device has safe access rights 4.814
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:331 6.930
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 10.000
And I start Tails from USB drive "old" with network unplugged and I login 1:14.272
Then Tails is running from USB drive "old" 0.458
And I create a persistent partition 47.118
And I take note of which tps features are available 1.556
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 10.322
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 3.696
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:22.898
Then Tails is running from USB drive "old" 0.655
And all tps features are active 2.479
When I write some files expected to persist 1.482
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 4.042
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 12.021
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.772
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.540
And I log in to a new session 12.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.873
And I plug USB drive "to_upgrade" 3.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.811
Then the running Tails is installed on USB drive "to_upgrade" 22.627
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:331 4.049
After features/support/hooks.rb:100 0.000
Tags: @product
1:43.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:31.746
Then all tps features from the old Tails version are active 2.142
And Tails is running from USB drive "to_upgrade" 0.432
And the boot device has safe access rights 4.234
And the expected persistent files created with the old Tails version are present in the filesystem 1.712
And all persistent directories from the old Tails version have safe access rights 3.269
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:17.459
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.921
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.057
And Tor is ready 19.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.695
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.556
Given I shutdown Tails and wait for the computer to power off 8.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.420
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.742
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.194
# 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.276
When the network is plugged 0.064
And Tor is ready 12.745
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.878
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.786
Given I shutdown Tails and wait for the computer to power off 7.924
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:32.602
cannot 
cannot find TailsGreeter.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:439:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:331 5.240 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:37:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4127/artifact/build-artifacts/01:37:06_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/4127/artifact/build-artifacts/01:37:06_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4127/artifact/build-artifacts/01:37:06_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4127/artifact/build-artifacts/01:37:06_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
51.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 40.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
After features/support/hooks.rb:331 0.936
After features/support/hooks.rb:100 0.000