Project Number Date
test_Tails_ISO_20619-wait-for-persistent-storage-check 3 23 Oct 2024, 18:15

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 18:7.717 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.158
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.684
When I start Tails from USB drive "old" with network unplugged 1:28.071
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.738
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.485
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login 1:23.575
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 32.288
And I take note of which tps features are available 1.444
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.749
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.429
Before features/support/hooks.rb:269 0.006
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.558
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.298
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.835
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.183
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.049
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.144
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.073
And I log in to a new session 20.249
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.538
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.019
Then the running Tails is installed on USB drive "to_upgrade" 21.415
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.370
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.760
Before features/support/hooks.rb:269 0.008
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.829
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.279
And the expected persistent files created with the old Tails version are present in the filesystem 1.720
And all persistent directories from the old Tails version have safe access rights 2.631
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:32.173
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.119
And no SquashFS delta is installed 0.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.575
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.097
And Tor is ready 48.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.137
Given I shutdown Tails and wait for the computer to power off 8.712
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.705
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.285
When the network is plugged 0.069
And Tor is ready 21.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.116
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.818
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.031
can 
can not find any of the patterns ["TailsGreeterLoginButton.png", "TailsGreeterLoginButtonGerman.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224:in `wait_any'
./features/step_definitions/common_steps.rb:490: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.452 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:46:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20619-wait-for-persistent-storage-check/3/artifact/build-artifacts/01:46:21_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_20619-wait-for-persistent-storage-check/3/artifact/build-artifacts/01:46:21_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20619-wait-for-persistent-storage-check/3/artifact/build-artifacts/01:46:21_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20619-wait-for-persistent-storage-check/3/artifact/build-artifacts/01:46:21_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.564
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 10.233
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.357
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 16.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.925
After features/support/hooks.rb:326 0.981
After features/support/hooks.rb:100 0.000