Project Number Date
test_Tails_ISO_stable 4630 23 Jan 2024, 13:36

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:54.538 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
1:32.305
Before features/support/hooks.rb:245 0.004
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 23.275
When I start Tails from USB drive "old" with network unplugged 1:3.853
Then the boot device has safe access rights 2.931
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.695
After features/support/hooks.rb:75 0.012
Tags: @product
2:2.291
Before features/support/hooks.rb:245 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:5.167
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 45.135
And I take note of which tps features are available 1.540
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 9.067
After features/support/hooks.rb:291 0.127
After features/support/hooks.rb:75 0.008
Tags: @product
2:31.254
Before features/support/hooks.rb:245 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.374
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.854
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.665
And all persistent directories from the old Tails version have safe access rights 2.728
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 3.086
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.494
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.007
Tags: @product
2:32.829
Before features/support/hooks.rb:245 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.312
And I log in to a new session 17.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.135
And I plug USB drive "to_upgrade" 2.612
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.340
Then the running Tails is installed on USB drive "to_upgrade" 12.641
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:291 6.839
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.951
Before features/support/hooks.rb:245 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.712
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.918
And the expected persistent files created with the old Tails version are present in the filesystem 1.843
And all persistent directories from the old Tails version have safe access rights 3.018
After features/support/hooks.rb:291 0.854
After features/support/hooks.rb:75 0.010
7:43.935
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.208
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.335
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.646
When the network is plugged 0.044
And Tor is ready 15.434
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.816
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.583
Given I shutdown Tails and wait for the computer to power off 5.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.970
Then Tails is running version 2.2~testoverlayfsng 0.125
And all tps features are active 2.159
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.391
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.317
When the network is plugged 0.033
And Tor is ready 15.047
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.972
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.863
Given I shutdown Tails and wait for the computer to power off 4.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:27.209
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:546:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:501: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:286: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 2.3~testoverlayfsng 0.000
And all tps features are active 0.000
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.000
And only the 2.3~testoverlayfsng 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 2.1~testoverlayfsng 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 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:291 4.893

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:50:54)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4630/artifact/build-artifacts/01:50:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4630/artifact/build-artifacts/01:50:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4630/artifact/build-artifacts/01:50:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4630/artifact/build-artifacts/01:50:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:75 0.019
27.969
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.885
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.381
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 0.810
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 13.057
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.743
After features/support/hooks.rb:291 0.607
After features/support/hooks.rb:75 0.000