Project Number Date
test_Tails_ISO_stable 4752 27 Mar 2024, 16:17

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
2:15.600
Scenario I can perform administrative tasks if I have set up an administration password in the Welcome Screen
Before features/support/hooks.rb:245 0.003
Steps
Given I have started Tails from DVD without network and logged in with an administration password 1:42.960
And running a command as root with pkexec requires PolicyKit administrator privileges 0.109
Then I can run a command as root with sudo 0.088
Then I can run a command as root with pkexec 32.442
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:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/common_steps.rb:763:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:781:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:799:in `/^I enter the "([^"]*)" password in the GNOME authentication prompt$/'
./features/step_definitions/common_steps.rb:758:in `/^I enter the sudo password in the GNOME authentication prompt$/'
./features/step_definitions/root_access_control.rb:50:in `/^I can run a command as root with pkexec$/'
features/root_access_control.feature:10:in `Then I can run a command as root with pkexec'
After features/support/hooks.rb:291 4.144

SCENARIO FAILED: 'I can perform administrative tasks if I have set up an administration password in the Welcome Screen' (at time 00:08:36)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:08:36_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:08:36_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:08:36_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:08:36_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal

After features/support/hooks.rb:75 0.008
2:9.372
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:245 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:9.372
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:450: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:449:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:288:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:148:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:145:in `each'
./features/step_definitions/snapshots.rb:145:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:168:in `block (2 levels) 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:449:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:288: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/step_definitions/snapshots.rb:148:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:145:in `each'
./features/step_definitions/snapshots.rb:145:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:133:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:168:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:76:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
And I wait 20 seconds 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:291 4.009

SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:33:00)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:33:00_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:33:00_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:33:00_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4752/artifact/build-artifacts/00:33:00_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:75 0.006