Project Number Date
test_Tails_ISO_stable 5054 28 Aug 2024, 12:12

Failures Overview

The following summary displays scenarios that failed.

6:52.740
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.177
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:18.360
And I configure APT to prefer an old version of cowsay 0.025
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 25.418
And I accept adding "cowsay" to Additional Software 6.822
And Additional Software is correctly configured for package "cowsay" 0.873
And I shutdown Tails and wait for the computer to power off 6.468
And I start Tails from USB drive "__internal" with network unplugged 57.093
And I enable persistence 11.197
# 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.024
And I log in to a new session 35.314
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.590
And I revert the APT tweaks that made it prefer an old version of cowsay 0.076
# 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.074
And the network is plugged 0.070
And Tor is ready 20.563
# 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 37.157
And available upgrades have been checked 0.317
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.115
And I can open the Additional Software configuration window from the notification 29.999
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:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:164:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:106: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:515 0.033
After features/support/hooks.rb:326 5.574

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:24:34_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_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_stable/5054/artifact/build-artifacts/01:24:34_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:24:34_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.016
Feature: Using Evince
Tags: @product
31.132
Scenario I can view and print a PDF file stored in /usr/share
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.222
When I open "/usr/share/cups/data/default-testpage.pdf" with Evince 4.435
Then I see "CupsTestPage.png" after at most 40 seconds 3.376
And I can print the current document to "/home/amnesia/output.pdf" 15.097
The
The document was not printed to /home/amnesia/output.pdf (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/evince.rb:27:in `/^I can print the current document to "([^"]+)"$/'
features/evince.feature:11:in `And I can print the current document to "/home/amnesia/output.pdf"'
After features/support/hooks.rb:326 4.996

SCENARIO FAILED: 'I can view and print a PDF file stored in /usr/share' (at time 01:57:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:57:41_I_can_view_and_print_a_PDF_file_stored_in__usr_share.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:57:41_I_can_view_and_print_a_PDF_file_stored_in__usr_share.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:57:41_I_can_view_and_print_a_PDF_file_stored_in__usr_share.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5054/artifact/build-artifacts/01:57:41_I_can_view_and_print_a_PDF_file_stored_in__usr_share.journal

After features/support/hooks.rb:100 0.000