Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 63 03 May 2024, 06:47

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:5.099
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:259 0.005
Before features/support/hooks.rb:456 0.007
Steps
Given a computer 0.219
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:17.422
And I configure APT to prefer an old version of cowsay 0.022
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.506
And I accept adding "cowsay" to Additional Software 6.794
And Additional Software is correctly configured for package "cowsay" 0.909
And I shutdown Tails and wait for the computer to power off 6.481
And I start Tails from USB drive "__internal" with network unplugged 59.198
And I enable persistence 12.733
# 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.025
And I log in to a new session 37.643
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.662
And I revert the APT tweaks that made it prefer an old version of cowsay 0.083
# 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.065
And the network is plugged 0.035
And Tor is ready 22.217
# 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 40.905
And available upgrades have been checked 0.562
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.083
And I can open the Additional Software configuration window from the notification 30.527
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:464 0.033
After features/support/hooks.rb:305 4.927 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:28:00)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_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/63/artifact/build-artifacts/01:28:00_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:89 0.018
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
21.554
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.349
Then the keys trusted by APT are valid for the next 3 months 13.204
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.309 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:13:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/63/artifact/build-artifacts/02:13:53_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/63/artifact/build-artifacts/02:13:53_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/63/artifact/build-artifacts/02:13:53_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/63/artifact/build-artifacts/02:13:53_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000