Project Number Date
test_Tails_ISO_stable 5239 31 Oct 2024, 09:00

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 21:4.831 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:6.824
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.921
When I start Tails from USB drive "old" with network unplugged 1:29.578
Then the boot device has safe access rights 3.032
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 3.527
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.386
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:22.770
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 32.199
And I take note of which tps features are available 1.828
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.272
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.214
Before features/support/hooks.rb:269 0.003
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.766
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.265
When I write some files expected to persist 1.754
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.528
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 4.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.846
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.463
Before features/support/hooks.rb:269 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 9.692
And I log in to a new session 19.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.693
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.415
Then the running Tails is installed on USB drive "to_upgrade" 23.540
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.135
After features/support/hooks.rb:100 0.000
Tags: @product
4:21.515
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:21.324
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:559:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:515:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295: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 4.926 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:45:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5239/artifact/build-artifacts/01:45:30_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5239/artifact/build-artifacts/01:45:30_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5239/artifact/build-artifacts/01:45:30_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/5239/artifact/build-artifacts/01:45:30_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.484
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.241
And no SquashFS delta is installed 0.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.067
And Tor is ready 22.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.495
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.960
Given I shutdown Tails and wait for the computer to power off 10.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.271
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.244
When the network is plugged 0.069
And Tor is ready 18.897
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.468
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.942
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.610
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.068
And Tor is ready 17.447
Then the Upgrader considers the system as up-to-date 0.356
# 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.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.192
After features/support/hooks.rb:326 1.034
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
41.941
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.981
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.734
After features/support/hooks.rb:326 0.952
After features/support/hooks.rb:100 0.000