Project Number Date
test_Tails_ISO_devel 3730 08 Mar 2025, 14:06

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 38:53.036 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:24.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.125
When I start Tails from USB drive "old" with network unplugged 1:45.618
Then the boot device has safe access rights 2.961
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.495
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:26.085
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.560
And I take note of which tps features are available 2.002
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 6.179
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.537
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.897
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.057
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.668
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 4.307
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.820
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.302
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.795
And I log in to a new session 21.265
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.514
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.524
Then the running Tails is installed on USB drive "to_upgrade" 20.391
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.992
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.346
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.916
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.042
And the expected persistent files created with the old Tails version are present in the filesystem 2.196
And all persistent directories from the old Tails version have safe access rights 2.512
After features/support/hooks.rb:330 1.163
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
25:52.803
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 11.477
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.616
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.082
And Tor is ready 20.777
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.623
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.911
Given I shutdown Tails and wait for the computer to power off 8.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.136
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 4.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.468
When the network is plugged 0.098
And Tor is ready 20.203
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.807
Given I shutdown Tails and wait for the computer to power off 4.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:59.083
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.898 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:50:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3730/artifact/build-artifacts/02:50:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3730/artifact/build-artifacts/02:50:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3730/artifact/build-artifacts/02:50:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.952
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 with a persistent partition enabled and logged in 9.862
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 21.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.144
After features/support/hooks.rb:330 0.865
After features/support/hooks.rb:100 0.000