Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 65 05 May 2024, 06:39

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
21.299
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.341
Then the keys trusted by APT are valid for the next 3 months 12.957
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.316

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/02:14:10_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/65/artifact/build-artifacts/02:14:10_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/65/artifact/build-artifacts/02:14:10_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/65/artifact/build-artifacts/02:14:10_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000
3:37.716
Scenario Watching a WebM video
Before features/support/hooks.rb:259 0.008
Before features/support/hooks.rb:456 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.890
When I start the Tor Browser 22.744
And the Tor Browser loads the startup page 3:0.082
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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:489:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:47:in `And the Tor Browser loads the startup page'
Then I can watch a WebM video in Tor Browser 0.000
After features/support/hooks.rb:464 0.031
After features/support/hooks.rb:305 5.519

SCENARIO FAILED: 'Watching a WebM video' (at time 04:01:20)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:01:20_Watching_a_WebM_video.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:01:20_Watching_a_WebM_video.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:01:20_Watching_a_WebM_video.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:01:20_Watching_a_WebM_video.journal

After features/support/hooks.rb:89 0.000
1:5.129
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 22.507
And I unlock and mount this VeraCrypt file container with GNOME Disks 42.621
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Authentication Required" roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/common_steps.rb:761:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:801:in `/^I cancel the GNOME authentication prompt$/'
./features/step_definitions/veracrypt.rb:253:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:305 4.652

SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 04:33:31)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:33:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:33:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:33:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/65/artifact/build-artifacts/04:33:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal

After features/support/hooks.rb:89 0.019