Project Number Date
test_Tails_ISO_5501-plaintext-locale-greeter 56 09 Jul 2025, 06:29

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 57:28.754 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
4:14.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.174
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 1:10.717
When I start Tails from USB drive "old" with network unplugged 2:46.340
Then the boot device has safe access rights 14.842
And Tails is running from USB drive "old" 0.576
And there is no persistence partition on USB drive "old" 0.104
And process "udev-watchdog" is running 0.179
And udev-watchdog is monitoring the correct device 0.454
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.860
After features/support/hooks.rb:100 0.010
Tags: @product
4:14.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 2:39.381
Then Tails is running from USB drive "old" 0.823
And I create a persistent partition 1:3.142
And I take note of which tps features are available 6.673
Then a Tails persistence partition exists on USB drive "old" 4.259
And I shutdown Tails and wait for the computer to power off 20.157
After features/support/hooks.rb:330 0.500
After features/support/hooks.rb:100 0.035
Tags: @product
6:2.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.393
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:34.160
Then Tails is running from USB drive "old" 3.335
And all tps features are active 3.451
When I write some files expected to persist 1.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.700
And all persistent directories from the old Tails version have safe access rights 3.639
And I take note of which tps features are available 1.623
And I shutdown Tails and wait for the computer to power off 10.616
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:1.915
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.014
Tags: @product
4:42.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 33.750
And I log in to a new session 38.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.513
And I plug USB drive "to_upgrade" 3.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:15.816
Then the running Tails is installed on USB drive "to_upgrade" 1:2.775
And I unplug USB drive "to_upgrade" 0.440
And I unplug USB drive "__internal" 0.316
After features/support/hooks.rb:330 7.315
After features/support/hooks.rb:100 0.000
Tags: @product
24:9.275
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.026
Steps
Given a computer 0.732
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 24:8.543
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:732:in `new'
./features/step_definitions/common_steps.rb:732: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: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:330 12.399 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:46:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/56/artifact/build-artifacts/02:46:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/56/artifact/build-artifacts/02:46:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/56/artifact/build-artifacts/02:46:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
12:24.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.036
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 42.749
And no SquashFS delta is installed 2.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.847
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.620
When the network is plugged 0.128
And Tor is ready 39.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 34.974
Given I shutdown Tails and wait for the computer to power off 15.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:45.469
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 4.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.521
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.465
# 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.345
When the network is plugged 0.072
And Tor is ready 34.075
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.510
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 20.481
Given I shutdown Tails and wait for the computer to power off 13.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:26.932
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 12.430
And the file system changes introduced in version 6.3~testoverlayfs are present 0.746
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.064
And Tor is ready 39.580
Then the Upgrader considers the system as up-to-date 0.434
# 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 28.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 8.560
After features/support/hooks.rb:330 1.085
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
1:40.581
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 51.364
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.322
And the signing key used by the Upgrader is outdated 1.190
But a current signing key is available on our website 0.000
When the network is plugged 0.726
And Tor is ready 27.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.871
After features/support/hooks.rb:330 1.520
After features/support/hooks.rb:100 0.000