Project Number Date
test_Tails_ISO_devel 3856 06 Jun 2025, 13:19

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 40:4.798 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.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.535
When I start Tails from USB drive "old" with network unplugged 1:44.108
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 10.252
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:30.999
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 35.750
And I take note of which tps features are available 2.202
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 9.015
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.144
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.149
Then Tails is running from USB drive "old" 0.693
And all tps features are active 2.112
When I write some files expected to persist 2.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.786
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.504
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.378
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.605
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 12.041
And I log in to a new session 19.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.014
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.750
Then the running Tails is installed on USB drive "to_upgrade" 25.312
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 3.624
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.504
Then all tps features from the old Tails version are active 1.844
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.682
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.674
After features/support/hooks.rb:330 1.278
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26:54.555
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 12.284
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.091
And Tor is ready 24.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.063
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.434
Given I shutdown Tails and wait for the computer to power off 1:15.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.102
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.950
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.152
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.362
When the network is plugged 0.079
And Tor is ready 19.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.648
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.549
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:0.603
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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:330 10.839 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:10:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3856/artifact/build-artifacts/02:10:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3856/artifact/build-artifacts/02:10:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3856/artifact/build-artifacts/02:10:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.255
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 10.701
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.533
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 22.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.466
After features/support/hooks.rb:330 4.066
After features/support/hooks.rb:100 0.000