Project Number Date
test_Tails_ISO_20522-ocr-more 14 23 Dec 2024, 05:39

Failures Overview

The following summary displays scenarios that failed.

Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:40.849
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
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 9.719
And I prepare Tails for memory erasure tests 0.583
And I fill a 128 MiB file with a known pattern on the persistent filesystem 25.825
And patterns cover at least 100 MiB in the guest's memory 3.729 
Pattern coverage: 113.316% (113 MiB out of 100 MiB reference memory)
When I eject the boot medium 0.567
Then I see a window explaining me the danger of unplugging the USB stick 1:0.423
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/erase_memory.rb:262: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/erase_memory.rb:262:in `/^I see a window explaining me the danger of unplugging the USB stick$/'
features/emergency_shutdown.feature:53:in `Then I see a window explaining me the danger of unplugging the USB stick'
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:326 10.558 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:54:22)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/01:54:22_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/01:54:22_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/01:54:22_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.295
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.207
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.475
When Tails detects disk read failures on the SquashFS 0.609
Then I see a disk failure message 10.002
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.751 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:09:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:05_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/14/artifact/build-artifacts/02:09:05_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:05_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:05_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.236
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.237
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.133
When Tails detects disk read failures on the boot device 0.863
Then I see a disk failure message 10.002
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.530 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:09:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:32_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/14/artifact/build-artifacts/02:09:32_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:32_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:32_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.185
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.003
Steps
Given a computer 0.227
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.231
When Tails detects disk read failures on the boot device with a target error 0.725
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.545 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:09:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:58_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/14/artifact/build-artifacts/02:09:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/02:09:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
22:27.447
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
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 10.976
Then Tails is running from USB drive "__internal" 0.658
And all tps features are active 2.615
And all persistent directories have safe access rights 2.609
When I disable the first tps feature 5.199
Then all tps features but the first one are active 2.516
And I shutdown Tails and wait for the computer to power off 8.294
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:54.576
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.824 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:24:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/03:24:49_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_20522-ocr-more/14/artifact/build-artifacts/03:24:49_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_20522-ocr-more/14/artifact/build-artifacts/03:24:49_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.007
Feature: Using persistent Tor bridges and pluggable transports
2:36.712
Background
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.013
And I create a persistent partition with the default settings 17.004
Then the "TorConfiguration" tps feature is not enabled 1.071
When the network is plugged 0.076
And the Tor Connection Assistant autostarts 7.318
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.575
And I wait until Tor is ready 1.213
Then tca.conf includes the configured bridges 0.012
And the "TorConfiguration" tps feature is enabled and active 2.593
When I cold reboot the computer 9.564
And the computer reboots Tails 1:35.269
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:451: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/common_steps.rb:450: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/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
features/persistent_tor_bridges.feature:18:in `And the computer reboots Tails'
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 4.849 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:00:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:00:53_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:00:53_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:00:53_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:00:53_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.035
Feature: Browsing the web using the Tor Browser
Tags: @product
53.300
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.590
Then the amnesiac Downloads directory exists 0.095
And there is a GNOME bookmark for the amnesiac Downloads directory 1.676
Then I start the Tor Browser in offline mode 28.603
And I can save the current page as "index.html" to the Downloads GNOME bookmark 14.334
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:143:in `And I can save the current page as "index.html" to the Downloads 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 5.992 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 04:32:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:32:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:32:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:32:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:32:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
57.946
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 15.959
And I unlock and mount this VeraCrypt file container with GNOME Disks 41.987
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:84: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.542 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 04:59:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:59:13_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:59:13_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:59:13_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/14/artifact/build-artifacts/04:59:13_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000