Cucumber Reports (no 5117) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5117	25 Sep 2024, 08:53

Feature: Additional software

11:7.454

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:269 0.004

Before features/support/hooks.rb:507 0.004

Steps

Given a computer 0.218

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:27.998

And I configure APT to prefer an old version of cowsay 0.034

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 29.203

And I accept adding "cowsay" to Additional Software 4.360

And Additional Software is correctly configured for package "cowsay" 0.847

And I shutdown Tails and wait for the computer to power off 6.018

And I start Tails from USB drive "__internal" with network unplugged 1:1.852

And I enable persistence 13.155

# 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.035

And I log in to a new session 38.607

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.815

And I revert the APT tweaks that made it prefer an old version of cowsay 0.053

# 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.067

And the network is plugged 0.080

And Tor is ready 21.475

# 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 8.910

And available upgrades have been checked 0.175

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 5:2.545

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:595:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:105:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'

And I can open the Additional Software configuration window from the notification 0.000

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

Hooks

After features/support/hooks.rb:515 0.033

After features/support/hooks.rb:326 8.877

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:32:38)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5117/artifact/build-artifacts/01:32:38_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/5117/artifact/build-artifacts/01:32:38_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/5117/artifact/build-artifacts/01:32:38_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

1:4.726

Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 22.811

And I unlock and mount this VeraCrypt file container with GNOME Disks 41.915

The

The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Authentication Required" roleName='label'
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/common_steps.rb:765:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:805:in `/^I cancel the GNOME authentication prompt$/'
./features/step_definitions/veracrypt.rb:253:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'

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

Hooks

After features/support/hooks.rb:326 7.898

Output 1

SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 04:48:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5117/artifact/build-artifacts/04:48:06_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5117/artifact/build-artifacts/04:48:06_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5117/artifact/build-artifacts/04:48:06_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5117/artifact/build-artifacts/04:48:06_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal

After features/support/hooks.rb:100 0.023