Project Number Date
test_Tails_ISO_devel 3583 10 Nov 2024, 13:00

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 61 1 25 0 0 87 6 1 7 37:23.713 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:21.876
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 38.588
When I start Tails from USB drive "old" with network unplugged 1:37.496
Then the boot device has safe access rights 3.431
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 6.980
After features/support/hooks.rb:100 0.011
Tags: @product
2:9.944
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:25.842
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.733
And I take note of which tps features are available 1.620
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 8.289
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.014
Tags: @product
3:9.150
Before features/support/hooks.rb:269 0.008
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.290
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.224
When I write some files expected to persist 1.898
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.562
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.545
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.848
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.488
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.485
And I log in to a new session 22.110
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.975
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.136
Then the running Tails is installed on USB drive "to_upgrade" 20.908
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.880
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.243
Then all tps features from the old Tails version are active 1.623
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.458
And all persistent directories from the old Tails version have safe access rights 2.824
After features/support/hooks.rb:326 0.637
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24:5.132
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 13.197
And no SquashFS delta is installed 0.296
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.077
And Tor is ready 51.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22:58.478
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderDownloadComplete.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1320:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:91:in `And I can successfully install the incremental upgrade to version 6.2~testoverlayfs'
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.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.752 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_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_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
39.241
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 1.058
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 19.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.027
After features/support/hooks.rb:326 1.547
After features/support/hooks.rb:100 0.000