Project Number Date
test_Tails_ISO_stable 4859 29 May 2024, 13:34

Failures Overview

The following summary displays scenarios that failed.

5:21.827
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.642
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.550
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.035
And Tor is ready 17.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.038
Given I shutdown Tails and wait for the computer to power off 8.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.260
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.307
When the network is plugged 0.044
And Tor is ready 18.388
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.145
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.393
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:448:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:79:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:67:in `loop'
./features/support/helpers/misc_helpers.rb:67:in `block in try_for'
./features/support/helpers/misc_helpers.rb:66:in `try_for'
./features/step_definitions/common_steps.rb:447:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:286:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/common_steps.rb:447:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:286: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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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 4.188

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:51:23)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/01:51:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/01:51:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/01:51:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/01:51:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:89 0.024
Tags: @product
21.611
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.110
Then the keys trusted by APT are valid for the next 3 months 13.501
The
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.467

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:14:55)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/02:14:55_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/02:14:55_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/02:14:55_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4859/artifact/build-artifacts/02:14:55_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000