Project Number Date
test_Tails_ISO_stable 5502 07 Mar 2025, 23:51

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 35:47.149 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:23.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.209
When I start Tails from USB drive "old" with network unplugged 1:47.898
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 6.990
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:21.823
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.169
And I take note of which tps features are available 1.505
Then a Tails persistence partition exists on USB drive "old" 0.729
And I shutdown Tails and wait for the computer to power off 8.222
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.728
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.646
Then Tails is running from USB drive "old" 0.680
And all tps features are active 1.884
When I write some files expected to persist 1.673
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.264
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.717
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.908
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.699
And I log in to a new session 17.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.712
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.987
Then the running Tails is installed on USB drive "to_upgrade" 19.992
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 2.199
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.490
Then all tps features from the old Tails version are active 1.536
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.281
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:330 1.086
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
23:1.442
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.880
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.544
When the network is plugged 0.073
And Tor is ready 22.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.780
Given I shutdown Tails and wait for the computer to power off 8.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:58.349
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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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.821 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:04:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5502/artifact/build-artifacts/02:04:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5502/artifact/build-artifacts/02:04:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5502/artifact/build-artifacts/02:04:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
42.964
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 11.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 26.325
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.952
After features/support/hooks.rb:330 0.812
After features/support/hooks.rb:100 0.000