Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 32 06 Apr 2024, 06:19

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:26.322
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.008
Before features/support/hooks.rb:456 0.006
Steps
Given a computer 0.214
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:9.523
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 23.367
And I accept adding "cowsay" to Additional Software 6.521
And Additional Software is correctly configured for package "cowsay" 0.783
And I shutdown Tails and wait for the computer to power off 6.406
And I start Tails from USB drive "__internal" with network unplugged 55.352
And I enable persistence 10.818
# 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 34.941
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.454
And I revert the APT tweaks that made it prefer an old version of cowsay 0.075
# 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.075
And the network is plugged 0.040
And Tor is ready 19.319
# 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.699
And available upgrades have been checked 0.411
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.022
And I can open the Additional Software configuration window from the notification 29.245
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.047
After features/support/hooks.rb:305 4.899 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:21:24)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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/32/artifact/build-artifacts/01:21:24_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.022
Feature: Tails persistence
Tags: @product
1:37.262
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.915
And the network is plugged 0.080
And Tor is ready 15.782
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.185
And I shutdown Tails and wait for the computer to power off 6.644
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.653
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/support/helpers/dogtail.rb:353:in `grabFocus'
./features/step_definitions/usb.rb:639:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:650:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:290: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:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:305 3.967 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 02:53:57)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/32/artifact/build-artifacts/02:53:57_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/32/artifact/build-artifacts/02:53:57_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/32/artifact/build-artifacts/02:53:57_Creating_and_using_a_persistent_NetworkManager_connection.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/32/artifact/build-artifacts/02:53:57_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:89 0.008