Project Number Date
test_Tails_ISO_stable 5069 04 Sep 2024, 17:32

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:27.424
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.007
Before features/support/hooks.rb:507 0.007
Steps
Given a computer 0.226
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:33.077
And I configure APT to prefer an old version of cowsay 0.033
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 29.381
And I accept adding "cowsay" to Additional Software 4.682
And Additional Software is correctly configured for package "cowsay" 1.019
And I shutdown Tails and wait for the computer to power off 6.625
And I start Tails from USB drive "__internal" with network unplugged 1:3.040
And I enable persistence 13.119
# 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.043
And I log in to a new session 40.494
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.293
And I revert the APT tweaks that made it prefer an old version of cowsay 0.063
# 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.079
And the network is plugged 0.070
And Tor is ready 18.954
# 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 41.727
And available upgrades have been checked 0.603
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.100
And I can open the Additional Software configuration window from the notification 31.786
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.052
After features/support/hooks.rb:326 5.671 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:30:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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/5069/artifact/build-artifacts/01:30:17_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.019
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
20.366
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.934
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 3.432
The 
The Dogtail init script raised: AttributeError: can't set attribute
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:209:in `set_field'
./features/support/helpers/dogtail.rb:241:in `text='
./features/step_definitions/common_steps.rb:1660:in `select_path_in_file_chooser'
./features/step_definitions/veracrypt.rb:171:in `/^I unlock and mount this VeraCrypt (volume|file container) with Unlock VeraCrypt Volumes$/'
features/veracrypt.feature:32:in `And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:326 5.366 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 04:42:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5069/artifact/build-artifacts/04:42:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5069/artifact/build-artifacts/04:42:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5069/artifact/build-artifacts/04:42:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5069/artifact/build-artifacts/04:42:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000