Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 18 23 Mar 2024, 06:27

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
2:23.728
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.001
Steps
Given I have started Tails from DVD without network and logged in with an administration password 1:50.741
And running a command as root with pkexec requires PolicyKit administrator privileges 0.117
Then I can run a command as root with sudo 0.094
Then I can run a command as root with pkexec 32.774
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 5.135

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/00:08:39_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_20268-more-early-patch-functionality/18/artifact/build-artifacts/00:08:39_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_20268-more-early-patch-functionality/18/artifact/build-artifacts/00:08:39_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_20268-more-early-patch-functionality/18/artifact/build-artifacts/00:08:39_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.005
6:24.823
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:245 0.006
Before features/support/hooks.rb:442 0.006
Steps
Given a computer 0.225
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:8.637
And I configure APT to prefer an old version of cowsay 0.075
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 23.473
And I accept adding "cowsay" to Additional Software 5.235
And Additional Software is correctly configured for package "cowsay" 0.863
And I shutdown Tails and wait for the computer to power off 6.037
And I start Tails from USB drive "__internal" with network unplugged 53.850
And I enable persistence 12.586
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.023
And I log in to a new session 34.309
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.047
And I revert the APT tweaks that made it prefer an old version of cowsay 0.051
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.055
And the network is plugged 0.043
And Tor is ready 20.628
# Note: the next step races against the appearance of the "The
# upgrade of your additional software failed" notification.
# It should win most of the time, which is good, but there's no
# guarantee it does. If it loses, then it'll remove the notification
# we'll be trying to interact with below ("I can open…")
And all notifications have disappeared 36.489
And available upgrades have been checked 0.631
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.085
And I can open the Additional Software configuration window from the notification 29.473
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Configure" roleName='push button'
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/additional_software_packages.rb:44:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:167:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:102:in `And I can open the Additional Software configuration window from the notification'
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:450 0.032
After features/support/hooks.rb:291 4.692

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:21:51)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/01:21:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:75 0.022
3:58.831
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 10.644
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.321
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.318
When I accept the autoconfiguration wizard's configuration 3:47.546
The
The Dogtail init script raised: SearchError: descendent of [frame | Account Setup - Mozilla Thunderbird]: "Get Messages" button
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:268:in `button'
./features/step_definitions/thunderbird.rb:128:in `/^I fetch my email$/'
./features/step_definitions/thunderbird.rb:160:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
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
After features/support/hooks.rb:450 0.042
After features/support/hooks.rb:291 5.142

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/03:33:00_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/03:33:00_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/03:33:00_I_can_send_emails,_and_receive_emails_over_IMAP.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/18/artifact/build-artifacts/03:33:00_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:75 0.000