Project Number Date
test_Tails_ISO_devel 4067 11 Nov 2025, 17:16

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:13.169 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:7.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 33.162
When I start Tails from USB drive "old" with network unplugged 1:28.582
Then the boot device has safe access rights 3.626
And Tails is running from USB drive "old" 0.485
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:331 3.601
After features/support/hooks.rb:100 0.014
Tags: @product
2:9.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:27.799
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 31.376
And I take note of which tps features are available 1.505
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 7.822
After features/support/hooks.rb:331 0.686
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.610
Then Tails is running from USB drive "old" 0.699
And all tps features are active 2.162
When I write some files expected to persist 1.530
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.527
And all persistent directories from the old Tails version have safe access rights 2.564
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 7.789
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.530
After features/support/hooks.rb:331 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.530
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 13.366
And I log in to a new session 18.000
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.545
And I plug USB drive "to_upgrade" 2.323
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.016
Then the running Tails is installed on USB drive "to_upgrade" 22.886
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 4.076
After features/support/hooks.rb:100 0.000
Tags: @product
1:51.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.305
Then all tps features from the old Tails version are active 1.925
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.424
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:331 0.618
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:41.221
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.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.464
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.076
And Tor is ready 15.436
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.177
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.111
Given I shutdown Tails and wait for the computer to power off 11.990
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.542
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.495
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.294
When the network is plugged 0.065
And Tor is ready 11.693
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.955
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.548
Given I shutdown Tails and wait for the computer to power off 7.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:32.908
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:484:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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.232 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:45:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4067/artifact/build-artifacts/01:45:20_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/4067/artifact/build-artifacts/01:45:20_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4067/artifact/build-artifacts/01:45:20_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4067/artifact/build-artifacts/01:45:20_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
26.096
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 with a persistent partition enabled and logged in 12.538
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 11.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.979
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.000