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

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 17 1 25 0 0 43 1 1 2 7:42.454 Failed
Feature: Upgrading an old Tails USB installation
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
Feature: Upgrading an old Tails USB installation
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