Cucumber Reports (no 50) - Failures Overview

Project	Number	Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests	50	22 Sep 2024, 07:17

Feature: Additional software

11:30.048

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.005

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.203

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

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 28.862

And I accept adding "cowsay" to Additional Software 4.685

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

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

And I start Tails from USB drive "__internal" with network unplugged 58.733

And I enable persistence 9.594

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

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

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.071

And the network is plugged 0.072

And Tor is ready 19.892

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

And available upgrades have been checked 0.104

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

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

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

And I start Tails from USB drive "__internal" with network unplugged 59.270

And I enable persistence 10.288

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

And I log in to a new session 38.785

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

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

And the network is plugged 0.084

And Tor is ready 1:1.395

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:648:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:603:in `/^Tor is ready$/'
features/additional_software_packages.feature:117:in `And Tor is ready'

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.056

After features/support/hooks.rb:326 14.343

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:43)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/01:32:43_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/01:32:43_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_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/01:32:43_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_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/01:32:43_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.027

Feature: Hardware failures

Tags: @product

1:38.564

Scenario Outline Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given a computer 0.220

And I start the computer from DVD with network unplugged 36.670

When Tails detects disk read failures on the boot device 1.502

Then I see a disk failure message on the splash screen 1:0.170

cannot

cannot find PlymouthDiskFailureMessage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/hardware.rb:62:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:15:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'

Hooks

After features/support/hooks.rb:326 4.754

Output 1

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 02:17:25)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/02:17:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/02:17:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/02:17:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/02:17:25_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal

After features/support/hooks.rb:100 0.008

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

30.652

Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile

Steps

When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 7.232

And I cancel the GNOME authentication prompt 1.970

And I unlock and mount this VeraCrypt volume with GNOME Disks 21.450

The

The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
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/veracrypt.rb:280:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume 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 volume 0.000

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:326 5.431

Output 1

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 04:59:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/04:59:29_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/04:59:29_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/04:59:29_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/50/artifact/build-artifacts/04:59:29_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal

After features/support/hooks.rb:100 0.000