Project Number Date
test_Tails_ISO_stable 5115 24 Sep 2024, 20:48

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:4.871
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.006
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.172
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:24.250
And I configure APT to prefer an old version of cowsay 0.026
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 25.766
And I accept adding "cowsay" to Additional Software 5.245
And Additional Software is correctly configured for package "cowsay" 0.898
And I shutdown Tails and wait for the computer to power off 6.539
And I start Tails from USB drive "__internal" with network unplugged 58.926
And I enable persistence 13.310
# 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.027
And I log in to a new session 44.422
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.631
And I revert the APT tweaks that made it prefer an old version of cowsay 0.056
# 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.062
And the network is plugged 0.096
And Tor is ready 23.155
# 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.336
And available upgrades have been checked 0.475
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.088
And I can open the Additional Software configuration window from the notification 31.381
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.039
After features/support/hooks.rb:326 5.670 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:23:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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/5115/artifact/build-artifacts/01:23:47_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.014
Feature: Tails persistence
Tags: @product
22:41.494
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.082
Then Tails is running from USB drive "__internal" 0.386
And all tps features are active 2.281
And all persistent directories have safe access rights 3.134
When I disable the first tps feature 5.772
Then all tps features but the first one are active 2.288
And I shutdown Tails and wait for the computer to power off 10.697
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:5.851
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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/common_steps.rb:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:301: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:49:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:326 10.891 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:19:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5115/artifact/build-artifacts/03:19:21_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5115/artifact/build-artifacts/03:19:21_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5115/artifact/build-artifacts/03:19:21_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.009