Project Number Date
test_Tails_ISO_20619-wait-for-persistent-storage-check 2 23 Oct 2024, 12:34

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 17:23.791 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:1.573
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.739
When I start Tails from USB drive "old" with network unplugged 1:26.702
Then the boot device has safe access rights 2.917
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 8.300
After features/support/hooks.rb:100 0.007
Tags: @product
2:2.375
Before features/support/hooks.rb:269 0.006
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:20.137
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.143
And I take note of which tps features are available 1.505
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 8.234
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.394
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.262
Then Tails is running from USB drive "old" 0.556
And all tps features are active 1.757
When I write some files expected to persist 3.098
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.481
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.241
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.784
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.256
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 10.070
And I log in to a new session 18.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.723
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.537
Then the running Tails is installed on USB drive "to_upgrade" 22.434
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 1.878
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.094
Before features/support/hooks.rb:269 0.006
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.047
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 2.208
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:9.017
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.439
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.065
And Tor is ready 18.269
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.298
Given I shutdown Tails and wait for the computer to power off 10.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.416
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.961
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.420
# 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.245
When the network is plugged 0.077
And Tor is ready 19.418
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.475
Given I shutdown Tails and wait for the computer to power off 4.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.452
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.496 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:40:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20619-wait-for-persistent-storage-check/2/artifact/build-artifacts/01:40: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/2/artifact/build-artifacts/01:40: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/2/artifact/build-artifacts/01:40: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/2/artifact/build-artifacts/01:40:21_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.079
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 9.874
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 1.197
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 18.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.765
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.000