Project Number Date
test_Tails_ISO_20522-ocr-more 6 16 Dec 2024, 05:21

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:23.296
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 10.670
And I wait until Tor is ready 1.529
When I disconnect the network through GNOME 2.649
And I connect the network through GNOME 2.657
Then the Tor Connection Assistant autostarts 2.370
And the Tor Connection Assistant connects to Tor 3.123
And I wait until Tor is ready 5:0.296
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:704:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:702:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:655:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 5.121 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/00:31:55_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.062
Feature: Installing Tails to a USB drive
Tags: @product
1:25.724
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:269 0.002
Steps
Given a computer 0.166
And I start Tails from USB drive "usbimage" with network unplugged and I login 1:25.558
can 
can not find any of the patterns ["TailsGreeterLoginButton.png", "TailsGreeterLoginButtonGerman.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:246:in `rescue in wait_any'
./features/support/helpers/screen.rb:230:in `wait_any'
./features/step_definitions/common_steps.rb:490: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/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_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:326 4.918 
SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:02:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/01:02:53_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/01:02:53_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/01:02:53_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/01:02:53_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product @doc
21.729
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.184
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.042
When Tails detects disk read failures on the SquashFS 0.500
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:27:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.465 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:10:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:32_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_20522-ocr-more/6/artifact/build-artifacts/02:10:32_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:32_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:32_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
21.469
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.007
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 9.546
When Tails detects disk read failures on the boot device 1.665
Then I see a disk failure message 10.063
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:28:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.432 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:10:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:59_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_20522-ocr-more/6/artifact/build-artifacts/02:10:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:10:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.490
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.221
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.596
When Tails detects disk read failures on the boot device with a target error 0.670
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.815 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:11:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:11:24_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_20522-ocr-more/6/artifact/build-artifacts/02:11:24_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:11:24_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/02:11:24_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:18.150
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:269 0.005
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.899
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 4.573
And Tails detects disk read failures on the boot device 1.484
When I try to enable persistence 0.595
Then the Welcome Screen tells me that my hardware is probably failing 4.867
When I log in to a new session 22.918
And all notifications have disappeared 4.760
Then the Tor Browser starts 30.051
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/browser.rb:465:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 6.829 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 03:34:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/03:34:49_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/03:34:49_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/03:34:49_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/03:34:49_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:46.574
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.427
And the network is plugged 0.217
And I successfully configure Tor 22.958
And available upgrades have been checked 0.074
And all notifications have disappeared 4.532
Then the persistent Tor Browser directory exists 0.053
And there is a GNOME bookmark for the persistent Tor Browser directory 1.849
When I start the Tor Browser 24.380
And I open the address "https://tails.net/about" in the Tor Browser 19.727
And "Tails - How Tails works" has loaded in the Tor Browser 1.236
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 19.114
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: Error: atspi_error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (1)
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:358:in `block in grabFocus'
./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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554: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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark'
And I open the address "file:///home/amnesia/Persistent/Tor Browser/index.html" 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 Tor Browser directory 0.000
After features/support/hooks.rb:326 6.787 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:13:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:13:19_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:13:19_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:13:19_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:13:19_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
52.909
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails from DVD without network and logged in 8.031
Then the amnesiac Pictures directory exists 0.044
And there is a GNOME bookmark for the amnesiac Pictures directory 1.771
Then I start the Tor Browser in offline mode 28.235
And I can save the current page as "index.html" to the Pictures GNOME bookmark 14.827
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: AttributeError: 'NoneType' object has no attribute 'querySelection'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:205:in `get_field'
./features/support/helpers/dogtail.rb:233:in `selected?'
./features/step_definitions/browser.rb:560: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/browser.rb:558: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/browser.rb:558:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:145:in `And I can save the current page as "index.html" to the Pictures GNOME bookmark'
features/torified_browsing.feature:139:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:326 6.609 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 04:16:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:16:49_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:16:49_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:16:49_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:16:49_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:3.778
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.609
And I unlock and mount this VeraCrypt file container with GNOME Disks 41.168
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: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/common_steps.rb:762:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:802:in `/^I cancel the GNOME authentication prompt$/'
./features/step_definitions/veracrypt.rb:242: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:326 5.691 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 04:39:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:39:42_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:39:42_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:39:42_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/6/artifact/build-artifacts/04:39:42_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014