Project Number Date
test_Tails_ISO_stable 4987 01 Aug 2024, 13:05

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 41:42.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
2:56.589
Before features/support/hooks.rb:269 0.008
Given a computer 0.314
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 1:4.184
When I start Tails from USB drive "old" with network unplugged 1:46.708
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.179
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 8.485
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.890
Before features/support/hooks.rb:269 0.006
Given a computer 0.931
And I start Tails from USB drive "old" with network unplugged and I login 1:28.890
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 35.661
And I take note of which tps features are available 2.240
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.930
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.026
Tags: @product
3:19.565
Before features/support/hooks.rb:269 0.015
Given a computer 0.296
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.902
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.252
When I write some files expected to persist 2.188
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.442
And I take note of which tps features are available 3.139
And I shutdown Tails and wait for the computer to power off 4.746
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.464
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.772
Before features/support/hooks.rb:269 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 23.017
And I log in to a new session 20.740
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.618
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.989
Then the running Tails is installed on USB drive "to_upgrade" 21.550
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 5.056
After features/support/hooks.rb:100 0.000
Tags: @product
22:16.561
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.263
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 22:16.298
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:706:in `new'
./features/step_definitions/common_steps.rb:706:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:292: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:326 10.861 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:03:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4987/artifact/build-artifacts/02:03:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4987/artifact/build-artifacts/02:03:59_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/4987/artifact/build-artifacts/02:03:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:25.244
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.641
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.547
When the network is plugged 0.358
And Tor is ready 21.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.391
Given I shutdown Tails and wait for the computer to power off 9.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.638
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.581
And the file system changes introduced in version 6.2~testoverlayfs are present 0.388
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.470
# 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.443
When the network is plugged 0.064
And Tor is ready 20.078
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.927
Given I shutdown Tails and wait for the computer to power off 6.997
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.026
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.217
And the file system changes introduced in version 6.3~testoverlayfs are present 0.691
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.530
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.581
And Tor is ready 17.265
Then the Upgrader considers the system as up-to-date 0.331
# 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 15.476
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.159
After features/support/hooks.rb:326 0.902
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.130
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.486
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.882
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 19.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.488
After features/support/hooks.rb:326 1.923
After features/support/hooks.rb:100 0.000