Cucumber Reports (no 4820) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4820	01 May 2024, 13:37

Feature: System memory erasure on shutdown

56.017

Scenario Erasure of the overlayfs read-write branch on shutdown

Hooks

Before features/support/hooks.rb:259 0.002

Steps

Given I have started Tails from DVD without network and logged in 8.153

And I prepare Tails for memory erasure tests 0.431

When I fill a 128 MiB file with a known pattern on the root filesystem 18.568

# ensure the pattern is in memory due to tmpfs, not to disk cache

And I drop all kernel caches 1.856

Then patterns cover at least 128 MiB in the guest's memory 3.401

Output 1

Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)

When I trigger shutdown 0.012

And I wait 20 seconds 20.017

Output 1

Slept for 20 seconds

Then I find very few patterns in the guest's memory 3.575

11.020%

11.020% of the free memory still has the pattern, but less than 0.800% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:219:in `/^I find very few patterns in the guest's memory$/'
features/erase_memory.feature:73:in `Then I find very few patterns in the guest's memory'

Output 1

Pattern coverage: 11.020% (99 MiB out of 900 MiB reference memory)

Hooks

After features/support/hooks.rb:305 9.750

Output 1

SCENARIO FAILED: 'Erasure of the overlayfs read-write branch on shutdown' (at time 00:31:57)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/00:31:57_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/00:31:57_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.mkv

After features/support/hooks.rb:89 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow

7:40.262

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

Before features/support/hooks.rb:259 0.003

Before features/support/hooks.rb:456 0.003

Steps

Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:33.172

And I update APT using apt 19.336

And I install "popularity-contest" using apt 25.756

Then I am proposed to add the "popularity-contest" package to my Additional Software 7.574

When I create a persistent storage and activate the Additional Software feature 25.599

Then Additional Software is correctly configured for package "popularity-contest" 1.989

When I shutdown Tails and wait for the computer to power off 14.083

And I start Tails from USB drive "__internal" with network unplugged 1:5.254

And I enable persistence 23.437

And I log in to a new session 3:4.057

cannot

cannot find GnomeApplicationsMenu.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/additional_software_packages.feature:37:in `And I log in to a new session'

And the Additional Software installation service has started 0.000

Then I am notified that the installation succeeded 0.000

And Additional Software is correctly configured for package "popularity-contest" 0.000

And the package "popularity-contest" is installed after Additional Software has been started 0.000

Hooks

After features/support/hooks.rb:464 0.030

After features/support/hooks.rb:305 4.792

Output 1

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:13:40)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:13:40_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:89 0.023

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

6:23.089

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:259 0.006

Before features/support/hooks.rb:456 0.007

Steps

Given a computer 0.184

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:19.995

And I configure APT to prefer an old version of cowsay 0.022

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 28.347

And I accept adding "cowsay" to Additional Software 4.734

And Additional Software is correctly configured for package "cowsay" 1.026

And I shutdown Tails and wait for the computer to power off 6.600

And I start Tails from USB drive "__internal" with network unplugged 59.671

And I enable persistence 11.335

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.023

And I log in to a new session 38.128

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.452

And I revert the APT tweaks that made it prefer an old version of cowsay 0.046

# We remove the newest package after it has been downloaded and before

# it is installed, so that the upgrade process fails

And I prepare the Additional Software upgrade process to fail 0.067

And the network is plugged 0.032

And Tor is ready 1:1.421

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:644:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:599:in `/^Tor is ready$/'
features/additional_software_packages.feature:97:in `And Tor is ready'

# Note: the next step races against the appearance of the "The

# upgrade of your additional software failed" notification.

# It should win most of the time, which is good, but there's no

# guarantee it does. If it loses, then it'll remove the notification

# we'll be trying to interact with below ("I can open…")

And all notifications have disappeared 0.000

And available upgrades have been checked 0.000

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000

And I can open the Additional Software configuration window from the notification 0.000

And I shutdown Tails and wait for the computer to power off 0.000

And I start Tails from USB drive "__internal" with network unplugged 0.000

And I enable persistence 0.000

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.000

And I log in to a new session 0.000

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000

And I revert the APT tweaks that made it prefer an old version of cowsay 0.000

And the network is plugged 0.000

And Tor is ready 0.000

Then the Additional Software upgrade service has started 0.000

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000

Hooks

After features/support/hooks.rb:464 0.031

After features/support/hooks.rb:305 7.415

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:28:28)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:28:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:89 0.020

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

3:9.893

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

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.620

And no SquashFS delta is installed 0.082

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413

When the network is plugged 0.045

And Tor is ready 22.212

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.541

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.899

Given I shutdown Tails and wait for the computer to power off 8.762

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.561

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93: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

Hooks

After features/support/hooks.rb:305 4.359

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:45:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:45:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:45:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/01:45:52_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:89 0.010

Feature: Tails-related cryptographic keys are up-to-date

Tags: @product

21.801

Scenario The included APT repository keys are up-to-date

Hooks

Before features/support/hooks.rb:259 0.005

Steps

Given I have started Tails from DVD without network and logged in 8.717

Then the keys trusted by APT are valid for the next 3 months 13.083

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'

Hooks

After features/support/hooks.rb:305 4.406

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/02:09:52_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/02:09:52_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/02:09:52_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/02:09:52_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000

Feature: Tails persistence

Tags: @product

2:41.533

Scenario Changing the Persistent Storage passphrase

Hooks

Before features/support/hooks.rb:259 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.514

# Note that if anything fails after the passphrase was changed and

# before it's changed back below, subsequent scenarios might fail

# because the Persistent Storage doesn't have the expected passphrase.

When I change the passphrase of the Persistent Storage 40.570

And I shutdown Tails and wait for the computer to power off 14.748

Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 1:35.701

try_for()

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/persistence.feature:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'

And I change the passphrase of the Persistent Storage back to the original 0.000

Hooks

After features/support/hooks.rb:305 4.004

Output 1

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:12:28)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:12:28_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:12:28_Changing_the_Persistent_Storage_passphrase.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:12:28_Changing_the_Persistent_Storage_passphrase.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:12:28_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:89 0.010

Feature: Tails persistence

Tags: @product

1:36.931

Scenario Feature activation fails

Hooks

Before features/support/hooks.rb:259 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.248

And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.083

When I try to enable persistence 0.291

Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 34.421

When I log in to a new session after having activated the Persistent Storage 42.001

And all notifications have disappeared 10.885

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93: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/persistence.feature:148:in `And all notifications have disappeared'

Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000

And all tps features are enabled 0.000

And all tps features but the first one are active 0.000

Hooks

After features/support/hooks.rb:305 4.454

Output 1

SCENARIO FAILED: 'Feature activation fails' (at time 03:17:35)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:17:35_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:17:35_Feature_activation_fails.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:17:35_Feature_activation_fails.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4820/artifact/build-artifacts/03:17:35_Feature_activation_fails.journal

After features/support/hooks.rb:89 0.000