Project Number Date
test_Tails_ISO_stable 4735 22 Mar 2024, 11:59

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:25.205
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.005
Steps
Given a computer 0.179
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:8.099
And I configure APT to prefer an old version of cowsay 0.023
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 23.336
And I accept adding "cowsay" to Additional Software 5.294
And Additional Software is correctly configured for package "cowsay" 0.858
And I shutdown Tails and wait for the computer to power off 6.020
And I start Tails from USB drive "__internal" with network unplugged 54.562
And I enable persistence 10.865
# 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 35.601
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.607
And I revert the APT tweaks that made it prefer an old version of cowsay 0.055
# 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.072
And the network is plugged 0.056
And Tor is ready 20.180
# 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.576
And available upgrades have been checked 0.480
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.070
And I can open the Additional Software configuration window from the notification 29.234
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.050
After features/support/hooks.rb:291 4.890 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:21:29)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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/4735/artifact/build-artifacts/01:21:29_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_stable/4735/artifact/build-artifacts/01:21:29_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_stable/4735/artifact/build-artifacts/01:21:29_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.020
Feature: Tails persistence
Tags: @product
5:17.615
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 13.473
Then Tails is running from USB drive "__internal" 0.344
When I create a file in the Persistent directory 0.119
And I create a persistent partition with the default settings 24.842
Then the file I created was copied to the Persistent Storage 0.711
When I shutdown Tails and wait for the computer to power off 10.102
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:28.021
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:560:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:516:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:294: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:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:291 4.379 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 02:51:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4735/artifact/build-artifacts/02:51:17_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4735/artifact/build-artifacts/02:51:17_Creating_a_Persistent_Storage.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4735/artifact/build-artifacts/02:51:17_Creating_a_Persistent_Storage.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4735/artifact/build-artifacts/02:51:17_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:75 0.041