Cucumber Reports (no 27) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable-flatpak	27	25 Sep 2026, 19:58

Feature: Time syncing

1:41.016

Scenario Anti-test: Changes to the hardware clock are kept when rebooting

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Before features/support/hooks.rb:527 0.002

Steps

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

When I bump the hardware clock's time with "-15 days" 1.827

And I warm reboot the computer 0.004

And the computer reboots Tails 1:33.057

can

can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:45:in `And the computer reboots Tails'

Then the hardware clock is still off by "-15 days" 0.000

Hooks

After features/support/hooks.rb:535 0.032

After features/support/hooks.rb:339 4.891

Output 1

SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:21:16)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:21:16_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:21:16_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:21:16_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:21:16_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal

After features/support/hooks.rb:108 0.033

Feature: Using Tor bridges and pluggable transports

Tags: @product

5:14.483

Scenario Using normal bridges

Steps

When I configure some normal bridges in the Tor Connection Assistant 12.160

Then I wait until Tor is ready 2.311

And tca.conf includes the configured bridges 0.005

And available upgrades have been checked 5:0.006

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:17:in `And available upgrades have been checked'

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:339 4.619

Output 1

SCENARIO FAILED: 'Using normal bridges' (at time 00:29:45)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:29:45_Using_normal_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:29:45_Using_normal_bridges.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:29:45_Using_normal_bridges.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:29:45_Using_normal_bridges.journal

After features/support/hooks.rb:108 0.066

Feature: Using Tor bridges and pluggable transports

Tags: @product @supports_real_tor

5:11.811

Scenario Default Tor bridges

Steps

When I configure the default bridges in the Tor Connection Assistant 10.027

Then I wait until Tor is ready 1.106

And Tor is configured to use the default bridges 0.669

And tca.conf includes no bridge 0.007

And available upgrades have been checked 5:0.000

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:40:in `And available upgrades have been checked'

And Tor is configured to use the default bridges 0.000

And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:339 4.997

Output 1

SCENARIO FAILED: 'Default Tor bridges' (at time 00:36:13)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:36:13_Default_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:36:13_Default_Tor_bridges.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:36:13_Default_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:36:13_Default_Tor_bridges.journal

After features/support/hooks.rb:108 0.037

Feature: Using Tor bridges and pluggable transports

Tags: @product

5:24.958

Scenario The same Tor configuration is applied when the network is reconnected

Steps

Given I configure a direct connection in the Tor Connection Assistant 5.506

And I wait until Tor is ready 1.718

When I disconnect the network through GNOME 8.808

And I connect the network through GNOME 6.735

Then the Tor Connection Assistant autostarts 0.057

And the Tor Connection Assistant connects to Tor 1.433

And I wait until Tor is ready 0.696

And Tor is using the same configuration as before 0.000

And available upgrades have been checked 5:0.000

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:80:in `And available upgrades have been checked'

And all Internet traffic has only flowed through Tor or connectivity check service 0.000

Hooks

After features/support/hooks.rb:339 4.664

Output 1

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:43:44)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:43:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:43:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:43:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:43:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:108 0.055

Feature: Using Tor bridges and pluggable transports

Tags: @product

5:11.786

Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection

Steps

Given the Moat distributor responds with the default bridges 0.101

When I configure Tor Connection to ask for bridge settings based on my location 5.586

And I wait until Tor is ready 6.098

And available upgrades have been checked 5:0.000

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:105:in `And available upgrades have been checked'

Then Tor is configured to use the default bridges 0.000

And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:339 5.098

Output 1

SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:50:44)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:50:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:50:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:50:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/00:50:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal

After features/support/hooks.rb:108 0.042

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

5:21.204

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Steps

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

And no SquashFS delta is installed 0.097

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

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

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

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

When the network is plugged 0.033

And Tor is ready 13.545

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

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

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

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

Then Tails is running version 6.2~testoverlayfs 0.004

And all tps features are active 7.446

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

And only the 6.2~testoverlayfs SquashFS delta is installed 0.038

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.089

# 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.164

When the network is plugged 0.036

And Tor is ready 10.174

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.889

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.212

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

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

Then Tails is running version 6.3~testoverlayfs 0.004

And all tps features are active 7.500

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

And only the 6.3~testoverlayfs SquashFS delta is installed 0.036

# 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.097

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160

When the network is plugged 0.034

And Tor is ready 10.274

Then the Upgrader considers the system as up-to-date 2:0.002

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'

# 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:339 4.649

Output 1

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

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:40:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:108 0.009

Feature: Tails documentation

Tags: @product @doc @not_release_blocker

3:36.140

Scenario The Tails documentation launcher works when online

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

Given I have started Tails from DVD and logged in and the network is connected 9.520

When I start "Tails Documentation" via GNOME Activities Overview 9.355

Then the Tor Browser has started 17.253

And "Tails - Documentation" has loaded in the Tor Browser 3:0.010

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:278:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:14:in `And "Tails - Documentation" has loaded in the Tor Browser'

Hooks

After features/support/hooks.rb:339 5.026

Output 1

SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 01:53:22)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:53:22_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:53:22_The_Tails_documentation_launcher_works_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:53:22_The_Tails_documentation_launcher_works_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/01:53:22_The_Tails_documentation_launcher_works_when_online.journal

After features/support/hooks.rb:108 0.000

Feature: Packages are up-to-date

Tags: @source @fragile

2.711

Scenario All packages are up-to-date

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:552 0.000

Steps

Given I have the build manifest for the image under test 0.000

Then all packages listed in the build manifest are up-to-date 2.711

Command

Command failed (pid 71977 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/tmp/tails-amd64-stable@9c783f99f9-20260925T1528Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/tmp/tails-amd64-stable@9c783f99f9-20260925T1528Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-09-25 18:05:03+00:00 (0:20:15.256618 ago)
INFO: Need to upgrade to a new APT snapshot:
  - jq (1.7.1-6+deb13u3) to Debian trixie-security (1.7.1-6+deb13u4)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:334:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:320:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:320:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/step_definitions/needed_package_updates.rb:10:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:13:in `Then all packages listed in the build manifest are up-to-date'

Hooks

After features/support/hooks.rb:559 0.000

After features/support/hooks.rb:108 0.000

Feature: Thunderbird email client

Tags: @product @check_tor_leaks

43.776

Scenario I can send emails, and receive emails over IMAP

Steps

When I enter my email credentials into the autoconfiguration wizard 43.531

Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.244

<false>

<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/thunderbird.rb:113:in `/^the autoconfiguration wizard's choice for the (incoming|outgoing) server is secure (.+)$/'
features/thunderbird.feature:22:in `Then the autoconfiguration wizard's choice for the incoming server is secure IMAP'

And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000

When I accept the autoconfiguration wizard's configuration 0.000

And I send an email to myself 0.000

And I fetch my email 0.000

Then I can find the email I sent to myself in my inbox 0.000

And the system only established connections with my email server 0.000

Hooks

After features/support/hooks.rb:535 0.037

After features/support/hooks.rb:339 5.323

Output 1

SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:26:47)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:26:47_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:26:47_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:26:47_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:26:47_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:108 0.008

Feature: Browsing the web using the Tor Browser

Tags: @product

3:31.633

Scenario The Tor Browser's circuit view feature works as expected

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

Given I have started Tails from DVD and logged in and the network is connected 9.358

When I start the Tor Browser 5.905

And I open the Tails homepage in the Tor Browser 16.243

Then the Tor Browser loads the Tails homepage 3:0.126

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:621:in `/^the Tor Browser loads the (Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:90:in `Then the Tor Browser loads the Tails homepage'

And Tor Browser's circuit view is working 0.000

Hooks

After features/support/hooks.rb:339 5.045

Output 1

SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 03:52:24)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:52:24_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:52:24_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:52:24_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:52:24_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:108 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:7.769

Scenario The Persistent directory is usable in Tor Browser

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

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

And the network is plugged 0.024

And I successfully configure Tor 9.783

And available upgrades have been checked 4.290

And all notifications have disappeared 2.510

And there is a GNOME bookmark for the Persistent directory 18.018

When I start the Tor Browser 6.137

And I download some file in the Tor Browser to the Persistent directory 18.901

The

The Dogtail init script raised: SearchError: descendant of [application | Firefox]: child with name='Opening tails-signing.key'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:356:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:109:in `And I download some file in the Tor Browser to the Persistent directory'

Then the file is saved to the Persistent directory 0.000

When I open the address "https://tails.net/about" in the Tor Browser 0.000

Then "Tails - How Tails works" has loaded in the Tor Browser 0.000

And I can print the current page as "output.pdf" to the Persistent directory 0.000

Hooks

After features/support/hooks.rb:339 5.310

Output 1

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 03:54:08)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:54:08_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:54:08_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:54:08_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/27/artifact/build-artifacts/03:54:08_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:108 0.000