Cucumber Reports (no 5459) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5459	15 Feb 2025, 08:55

Feature: Additional software

6:13.775

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

Steps

Given a computer 0.205

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

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

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

And I accept adding "cowsay" to Additional Software 6.499

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

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

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

And I enable persistence 12.248

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

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.103

And I log in to a new session 39.296

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

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

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

And the network is plugged 0.067

And Tor is ready 20.284

And available upgrades have been checked 0.055

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

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

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "tails-additional-software-config" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:165:in `new'
./features/step_definitions/additional_software_packages.rb:165:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103: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

Hooks

After features/support/hooks.rb:515 0.042

After features/support/hooks.rb:326 5.832

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20:43_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/5459/artifact/build-artifacts/01:20: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_stable/5459/artifact/build-artifacts/01:20: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_stable/5459/artifact/build-artifacts/01:20: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.022

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

3:9.315

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.004

Steps

Given a computer 0.200

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

And I enable persistence 13.985

And I remove the "cowsay" deb files from the APT cache 0.099

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.120

And I log in to a new session 43.909

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 10.623

And I can open the Additional Software log file from the notification 1:0.879

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-text-editor" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:171:in `new'
./features/step_definitions/additional_software_packages.rb:171:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/additional_software_packages.rb:170:in `block in <top (required)>' (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/additional_software_packages.rb:170:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'

And the package "cowsay" is not installed 0.000

Hooks

After features/support/hooks.rb:515 0.037

After features/support/hooks.rb:326 8.636

Output 1

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:23:59)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/01:23:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/01:23:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/01:23:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.007

Feature: Packages are up-to-date

Tags: @source

9.688

Scenario All packages are up-to-date

Hooks

Before features/support/hooks.rb:532 0.000

Steps

Given I have the build manifest for the image under test 0.000

Then all packages listed in the build manifest are up-to-date 9.688

Command

Command failed (returned pid 66329 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@3367737e1d-20250215T0314Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@3367737e1d-20250215T0314Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - onionshare (2.6.2-1~0.tails1) to Debian sid (2.6.2-5)
.
<0> expected but was
<#<Process::Status: pid 66329 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'

Hooks

After features/support/hooks.rb:539 0.000

After features/support/hooks.rb:100 0.000

Feature: Tor stream isolation is effective

Tags: @product @check_tor_leaks

3:22.121

Scenario The Tor Browser is using the web browser-specific SocksPort

Steps

When I monitor the network connections of Tor Browser 0.062

And I start the Tor Browser 21.966

And the Tor Browser loads the startup page 3:0.092

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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/tor_stream_isolation.feature:30:in `And the Tor Browser loads the startup page'

Then I see that Tor Browser is properly stream isolated 0.000

Hooks

After features/support/hooks.rb:515 0.042

After features/support/hooks.rb:326 5.833

Output 1

SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 04:11:23)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:11:23_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:11:23_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:11:23_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:11:23_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

3:34.248

Scenario Playing an Ogg audio track

Hooks

Before features/support/hooks.rb:269 0.008

Before features/support/hooks.rb:507 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.225

When I start the Tor Browser 20.922

And the Tor Browser loads the startup page 3:0.100

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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:40:in `And the Tor Browser loads the startup page'

Then I can listen to an Ogg audio track in Tor Browser 0.000

Hooks

After features/support/hooks.rb:515 0.029

After features/support/hooks.rb:326 5.730

Output 1

SCENARIO FAILED: 'Playing an Ogg audio track' (at time 04:18:08)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:18:08_Playing_an_Ogg_audio_track.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:18:08_Playing_an_Ogg_audio_track.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:18:08_Playing_an_Ogg_audio_track.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5459/artifact/build-artifacts/04:18:08_Playing_an_Ogg_audio_track.journal

After features/support/hooks.rb:100 0.000