Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 69 09 May 2024, 07:11

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 19 1 23 0 0 43 1 1 2 23:27.019 Failed
22:49.561
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.506
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.097
And Tor is ready 19.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.842
Given I shutdown Tails and wait for the computer to power off 8.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:53.721
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:305 9.931

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:10:18)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:10:18_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:10:18_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

After features/support/hooks.rb:89 0.008
37.458
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.926
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.537
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.660
After features/support/hooks.rb:305 0.732
After features/support/hooks.rb:89 0.000