Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 14 09 Nov 2024, 11:55

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 22:1.373 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:18.587
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.474
When I start Tails from USB drive "old" with network unplugged 1:41.591
Then the boot device has safe access rights 3.156
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.902
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.712
Before features/support/hooks.rb:269 0.005
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login 1:26.613
Then Tails is running from USB drive "old" 0.434
And I create a persistent partition 34.841
And I take note of which tps features are available 1.985
Then a Tails persistence partition exists on USB drive "old" 1.122
And I shutdown Tails and wait for the computer to power off 6.441
After features/support/hooks.rb:326 0.213
After features/support/hooks.rb:100 0.012
Tags: @product
3:26.265
Before features/support/hooks.rb:269 0.005
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:45.261
Then Tails is running from USB drive "old" 0.431
And all tps features are active 4.842
When I write some files expected to persist 1.704
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.610
And I take note of which tps features are available 0.611
And I shutdown Tails and wait for the computer to power off 4.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.470
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.147
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 11.583
And I log in to a new session 21.083
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.814
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.585
Then the running Tails is installed on USB drive "to_upgrade" 21.288
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.462
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.956
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.499
Then all tps features from the old Tails version are active 1.848
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.240
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.365
After features/support/hooks.rb:326 1.160
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:23.906
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.834
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.096
And Tor is ready 24.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.327
Given I shutdown Tails and wait for the computer to power off 13.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.858
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.631
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.294
When the network is plugged 0.077
And Tor is ready 21.333
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.236
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:25.860
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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:326 5.009 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:54:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/14/artifact/build-artifacts/01:54:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
43.797
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.703
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.864
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.919
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.000