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

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
40.760
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 40.760
try_for() 
try_for() timeout expired (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/tor.rb:648:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:480:in `tca_configure'
./features/step_definitions/tor.rb:611:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/tor_bridges.feature:28:in `When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode'
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:305 4.743 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:21:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:21:38_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:21:38_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:21:38_Using_obfs4_pluggable_transports_from_a_QR_code.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:21:38_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:89 0.073
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:10.394
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.071
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 30.939
Then the Tor Connection Assistant reports that it failed to connect 0.125
And tca.conf is empty 0.237
Given I scan a QR code from the error page in Tor Connection Assistant 37.021
try_for() 
try_for() timeout expired (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/tor.rb:722:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:305 5.556 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:23:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:23:06_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:23:06_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:23:06_TCA_can_scan_QR_code_after_a_connection_failure.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/00:23:06_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:89 0.053
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
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 
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
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
23.340
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.933
Then the keys trusted by APT are valid for the next 3 months 14.407
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.331 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:34:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:34:51_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:34:51_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:34:51_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:34:51_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:26.344
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.458
When I log in to a new session in French (fr) 3:17.886
cannot 
cannot find GnomeApplicationsMenuFrench.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:558:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:514:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:47:in `When I log in to a new session in French (fr)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "fr" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser in "fr" 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:305 4.428 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 02:50:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:50:51_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:50:51_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:50:51_Tails_is_localized_for_every_tier-1_language,_Examples___4_.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/69/artifact/build-artifacts/02:50:51_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:89 0.000