Project Number Date
test_Tails_ISO_stable 5505 10 Mar 2025, 17:24

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 22:28.344 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:4.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.843
And I create a 7200 MiB disk named "old" 0.241
And I plug USB drive "old" 1.187
And I write an old version of the Tails USB image to disk "old" 29.661
When I start Tails from USB drive "old" with network unplugged 1:28.591
Then the boot device has safe access rights 3.085
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.725
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:30.212
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 34.958
And I take note of which tps features are available 1.670
Then a Tails persistence partition exists on USB drive "old" 1.416
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.007
Tags: @product
2:59.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.728
Then Tails is running from USB drive "old" 0.491
And all tps features are active 1.901
When I write some files expected to persist 2.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
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.436
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.330
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.768
After features/support/hooks.rb:330 0.135
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.698
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.423
And I log in to a new session 18.962
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.642
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.873
Then the running Tails is installed on USB drive "to_upgrade" 22.818
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.111
After features/support/hooks.rb:100 0.000
Tags: @product
5:10.168
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.004
Steps
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 5:10.007
Remote 
Remote shell seems to be down (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/vm_helper.rb:548:in `wait_until_remote_shell_is_up'
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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 10.479 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:01:27)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5505/artifact/build-artifacts/02:01:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5505/artifact/build-artifacts/02:01:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5505/artifact/build-artifacts/02:01:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:26.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.603
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.518
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.621
When the network is plugged 0.062
And Tor is ready 21.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.562
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.600
Given I shutdown Tails and wait for the computer to power off 9.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.166
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.298
When the network is plugged 0.074
And Tor is ready 20.227
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.998
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.961
Given I shutdown Tails and wait for the computer to power off 4.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.885
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.047
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.064
And Tor is ready 16.960
Then the Upgrader considers the system as up-to-date 0.324
# 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 14.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.074
After features/support/hooks.rb:330 0.699
After features/support/hooks.rb:100 0.081
Tags: @product @automatic_upgrade
59.877
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 10.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 48.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
After features/support/hooks.rb:330 1.416
After features/support/hooks.rb:100 0.000