Project Number Date
test_Tails_ISO_stable 4570 16 Dec 2023, 12:02

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:24.580 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:19.992
Before features/support/hooks.rb:245 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 19.148
When I start Tails from USB drive "old" with network unplugged 55.682
Then the boot device has safe access rights 3.031
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.498
After features/support/hooks.rb:75 0.018
Tags: @product
1:50.339
Before features/support/hooks.rb:245 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 58.497
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 42.002
And I take note of which tps features are available 1.333
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 7.060
After features/support/hooks.rb:291 0.144
After features/support/hooks.rb:75 0.009
Tags: @product
2:7.813
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.129
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.306
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.661
And all persistent directories from the old Tails version have safe access rights 2.628
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 3.058
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.808
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.439
Before features/support/hooks.rb:245 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 9.884
And I log in to a new session 17.296
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.106
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.378
Then the running Tails is installed on USB drive "to_upgrade" 11.829
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.587
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.539
Before features/support/hooks.rb:245 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.764
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.459
And the expected persistent files created with the old Tails version are present in the filesystem 1.525
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:291 0.863
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
7:17.782
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.241
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.346
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.348
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.604
When the network is plugged 0.048
And Tor is ready 17.348
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.681
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 6:47.007
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.548 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:45:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4570/artifact/build-artifacts/01:45:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4570/artifact/build-artifacts/01:45:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4570/artifact/build-artifacts/01:45:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4570/artifact/build-artifacts/01:45:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:75 0.000
Tags: @product @automatic_upgrade
24.671
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.590
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.295
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.493
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 11.363
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.773
After features/support/hooks.rb:291 0.723
After features/support/hooks.rb:75 0.000