Project Number Date
test_Tails_ISO_stable 5178 12 Oct 2024, 12:38

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 19:0.465 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:27.942
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.087
When I start Tails from USB drive "old" with network unplugged 1:51.189
Then the boot device has safe access rights 3.277
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 7.058
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.772
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:25.962
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 35.262
And I take note of which tps features are available 1.632
Then a Tails persistence partition exists on USB drive "old" 0.962
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.107
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.131
Then Tails is running from USB drive "old" 0.724
And all tps features are active 2.347
When I write some files expected to persist 2.471
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.898
And I take note of which tps features are available 0.819
And I shutdown Tails and wait for the computer to power off 6.778
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.048
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.851
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 13.070
And I log in to a new session 20.711
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.997
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.398
Then the running Tails is installed on USB drive "to_upgrade" 26.781
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.593
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.705
Before features/support/hooks.rb:269 0.007
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.076
Then all tps features from the old Tails version are active 1.787
And Tails is running from USB drive "to_upgrade" 0.466
And the boot device has safe access rights 3.612
And the expected persistent files created with the old Tails version are present in the filesystem 1.857
And all persistent directories from the old Tails version have safe access rights 2.718
After features/support/hooks.rb:326 0.998
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:36.099
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.758
And no SquashFS delta is installed 0.211
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.741
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.554
When the network is plugged 0.115
And Tor is ready 25.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.950
Given I shutdown Tails and wait for the computer to power off 11.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:26.703
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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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.086 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:51:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_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_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.985
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 10.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 1.120
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.356
After features/support/hooks.rb:326 1.894
After features/support/hooks.rb:100 0.000