Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 15 13 Feb 2025, 20:05

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:8.995
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.204
And I start Tails from USB drive "__internal" with network unplugged 1:5.305
And I enable persistence 13.675
And I remove the "cowsay" deb files from the APT cache 0.071
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.118
And I log in to a new session 43.505
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5.430
And I can open the Additional Software log file from the notification 1:0.684
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-text-editor" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:171:in `new'
./features/step_definitions/additional_software_packages.rb:171:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/additional_software_packages.rb:170:in `block in <top (required)>' (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/additional_software_packages.rb:170:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.049
After features/support/hooks.rb:326 8.970 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:30:42)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:30:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:30:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:30:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:23.550
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.888
And I prepare Tails for memory erasure tests 0.645
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 37.972
And I fill the USB drive with a known pattern 1.552
And I read the content of the test FS 0.068
And patterns cover at least 99% of the test FS size in the guest's memory 3.805 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.300
And I wait for Tails to finish wiping the memory 1:30.317
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:326 10.603 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:57:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:57:06_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:57:06_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/01:57:06_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
3:44.992
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.701
When I start "Tails Documentation" via GNOME Activities Overview 11.087
Then the Tor Browser has started 24.102
Then "Tails - Documentation" has loaded in the Tor Browser 3:0.101
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:8:in `Then "Tails - Documentation" has loaded in the Tor Browser'
After features/support/hooks.rb:326 7.285 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 02:07:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:07:25_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:07:25_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:07:25_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:07:25_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:35.316
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.224
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.475
When Tails detects disk read failures on the SquashFS 0.984
Then I see a disk failure message 3.111
Then I can open the hardware failure documentation from the disk failure message 3:19.520
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:27:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 8.546 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:21:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:21:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:21:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:21:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:21:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:35.545
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.222
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.875
When Tails detects disk read failures on the boot device 2.033
Then I see a disk failure message 1.439
Then I can open the hardware failure documentation from the disk failure message 3:19.974
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:28:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 8.210 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:25:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:25:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:25:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:25:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:25:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:32.039
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.194
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.074
When Tails detects disk read failures on the boot device with a target error 2.040
Then I see a disk failure message 1.431
Then I can open the hardware failure documentation from the disk failure message 3:17.296
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:29:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 7.927 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:28:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:28:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:28:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:28:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/02:28:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
3.423
Scenario All packages are up-to-date
Before features/support/hooks.rb:532 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 3.423
Command 
Command failed (returned pid 58702 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/tmp/tails-amd64-10422-tor-browser-in-flatpak@4751c943d2+stable@ea007b7b15-20250213T1352Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/tmp/tails-amd64-10422-tor-browser-in-flatpak@4751c943d2+stable@ea007b7b15-20250213T1352Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1+deb12u1+tails1) to Debian trixie (1.16.0-1)
.
<0> expected but was
<#<Process::Status: pid 58702 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
23:1.805
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.174
Then Tails is running from USB drive "__internal" 0.914
And all tps features are active 2.484
And all persistent directories have safe access rights 3.159
When I disable the first tps feature 8.384
Then all tps features but the first one are active 3.711
And I shutdown Tails and wait for the computer to power off 13.382
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:12.594
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:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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:49:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:326 10.915 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:56:47)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/03:56:47_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/03:56:47_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/03:56:47_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.009
Feature: Tails persistence
Tags: @product @doc
4:55.408
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:269 0.012
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.882
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.117
When I try to enable persistence 0.289
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 33.022
When I repair the filesystem of the Persistent Storage 1.246
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.086
When I log in to a new session 46.624
And all notifications have disappeared 10.755
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.406
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.823
When I close the "whisperback" window 1.633
Then the Tor Browser starts 10.456
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 3:0.063
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/persistence.feature:202:in `And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser'
After features/support/hooks.rb:326 7.772 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:31:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:31:16_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:31:16_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:31:16_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:31:16_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
5:0.363
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.900
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 7.415
And Tails detects disk read failures on the boot device 1.565
When I try to enable persistence 0.409
Then the Welcome Screen tells me that my hardware is probably failing 20.061
When I log in to a new session 52.381
And all notifications have disappeared 9.496
Then the Tor Browser starts 20.099
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 3:0.035
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/persistence.feature:214:in `And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser'
After features/support/hooks.rb:326 6.541 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:36:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:36:25_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:36:25_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:36:25_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/15/artifact/build-artifacts/04:36:25_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000