Project Number Date
test_Tails_ISO_devel 4132 20 Dec 2025, 12:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 14:25.656 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
1:43.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.791
When I start Tails from USB drive "old" with network unplugged 1:6.250
Then the boot device has safe access rights 4.029
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.369
After features/support/hooks.rb:331 3.841
After features/support/hooks.rb:100 0.015
Tags: @product
1:40.410
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 2.818
And I start Tails from USB drive "old" with network unplugged and I login 1:1.567
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 28.683
And I take note of which tps features are available 1.194
Then a Tails persistence partition exists on USB drive "old" 0.739
And I shutdown Tails and wait for the computer to power off 5.114
After features/support/hooks.rb:331 0.320
After features/support/hooks.rb:100 0.009
Tags: @product
1:47.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.842
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.902
When I write some files expected to persist 1.511
# 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.395
And all persistent directories from the old Tails version have safe access rights 2.055
And I take note of which tps features are available 0.408
And I shutdown Tails and wait for the computer to power off 7.551
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.801
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.757
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 11.081
And I log in to a new session 15.989
And I clone USB drive "old" to a new USB drive "to_upgrade" 14.037
And I plug USB drive "to_upgrade" 2.792
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.687
Then the running Tails is installed on USB drive "to_upgrade" 19.852
And I unplug USB drive "to_upgrade" 1.101
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:331 3.801
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.513
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.409
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:33.103
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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:331 5.482 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:33:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4132/artifact/build-artifacts/01:33:42_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4132/artifact/build-artifacts/01:33:42_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4132/artifact/build-artifacts/01:33:42_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4132/artifact/build-artifacts/01:33:42_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:14.740
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 13.032
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.065
And Tor is ready 14.071
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.294
Given I shutdown Tails and wait for the computer to power off 10.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.706
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.259
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.261
When the network is plugged 0.056
And Tor is ready 13.070
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.581
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.025
Given I shutdown Tails and wait for the computer to power off 7.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.371
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.238
And Tor is ready 11.873
Then the Upgrader considers the system as up-to-date 0.139
# 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 5.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.465
After features/support/hooks.rb:331 0.904
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
25.564
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 with a persistent partition enabled and logged in 11.702
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.274
And Tor is ready 11.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.023
After features/support/hooks.rb:331 0.833
After features/support/hooks.rb:100 0.000