Project Number Date
test_Tails_ISO_devel 3197 17 Dec 2023, 12:10

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 17:33.531 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:27.068
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 19.561
When I start Tails from USB drive "old" with network unplugged 1:2.421
Then the boot device has safe access rights 2.916
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 3.694
After features/support/hooks.rb:75 0.008
Tags: @product
1:50.516
Before features/support/hooks.rb:245 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 57.849
Then Tails is running from USB drive "old" 0.475
And I create a persistent partition 42.592
And I take note of which tps features are available 1.515
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 7.163
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.010
Tags: @product
2:8.075
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.519
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.185
When I write some files expected to persist 1.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.625
And all persistent directories from the old Tails version have safe access rights 2.652
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 3.094
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.762
After features/support/hooks.rb:291 0.120
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.736
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.172
And I log in to a new session 15.484
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.609
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.751
Then the running Tails is installed on USB drive "to_upgrade" 13.715
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:291 6.561
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.659
Before features/support/hooks.rb:245 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.610
Then all tps features from the old Tails version are active 1.723
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.556
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.717
After features/support/hooks.rb:291 0.845
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
7:17.040
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:245 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.341
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.430
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.387
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.592
When the network is plugged 0.047
And Tor is ready 15.135
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.598
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 6:48.317
Tor 
Tor operation failed (despite retrying 10 times) with
Test::Unit::AssertionFailedError: <"TailsUpgraderDownloadComplete.png"> expected but was
<"TailsUpgraderFailure.png">. (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:1263: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 2.2~testoverlayfsng'
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 2.2~testoverlayfsng 0.000
And all tps features are active 0.000
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.000
And only the 2.2~testoverlayfsng 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_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.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 2.3~testoverlayfsng 0.000
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 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 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.483 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:49:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3197/artifact/build-artifacts/01:49:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3197/artifact/build-artifacts/01:49:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3197/artifact/build-artifacts/01:49:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3197/artifact/build-artifacts/01:49:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:75 0.000
Tags: @product @automatic_upgrade
24.434
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.616
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.268
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the signing key used by the Upgrader is outdated 0.545
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 12.210
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.695
After features/support/hooks.rb:291 0.649
After features/support/hooks.rb:75 0.000