Project Number Date
test_Tails_ISO_stable 4668 16 Feb 2024, 12:22

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 41 1 1 0 0 43 1 1 2 7:12.847 Failed
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
5:52.466
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.636
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.319
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.081
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.458
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.649
When the network is plugged 0.039
And Tor is ready 17.428
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.905
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.060
Given I shutdown Tails and wait for the computer to power off 5.462
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.250
Then Tails is running version 2.2~testoverlayfsng 0.095
And all tps features are active 2.451
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.473
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.410
When the network is plugged 0.041
And Tor is ready 13.913
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.866
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.964
Given I shutdown Tails and wait for the computer to power off 4.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.591
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.156
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.619
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.303
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.280
When the network is plugged 0.042
And Tor is ready 16.332
Then the Upgrader considers the system as up-to-date 0.340
# 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 27.032
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.111
After features/support/hooks.rb:291 0.796
After features/support/hooks.rb:75 0.040
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:20.380
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:245 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.216
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
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 1.277
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 1:9.450
The 
The system is not fully running yet:
No jobs running.

  UNIT               LOAD   ACTIVE SUB    DESCRIPTION
● session-c194.scope loaded failed failed Session c194 of user root

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 (RuntimeError)
./features/step_definitions/common_steps.rb:689:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:684:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:603:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.000
After features/support/hooks.rb:291 4.502 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:57:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4668/artifact/build-artifacts/01:57:38_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4668/artifact/build-artifacts/01:57:38_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4668/artifact/build-artifacts/01:57:38_Upgrading_a_Tails_whose_signing_key_is_outdated.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4668/artifact/build-artifacts/01:57:38_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:75 0.000