Cucumber Reports (no 5124) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5124	28 Sep 2024, 12:17

Feature: Additional software

6:51.654

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

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

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

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

And I accept adding "cowsay" to Additional Software 6.955

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

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

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

And I enable persistence 12.045

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

And I log in to a new session 40.207

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

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

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

And the network is plugged 0.067

And Tor is ready 20.161

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

And available upgrades have been checked 0.585

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

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

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

Hooks

After features/support/hooks.rb:515 0.045

After features/support/hooks.rb:326 5.510

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:23:27)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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/5124/artifact/build-artifacts/01:23:27_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.014

Feature: Browsing the web using the Tor Browser

Tags: @product

2:40.199

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.240

And all tps features are active 2.604

And all persistent filesystems have safe access rights 0.278

And all persistence configuration files have safe access rights 0.413

And all persistent directories have safe access rights 2.815

When I start the Tor Browser in offline mode 26.890

And I add a bookmark to eff.org in the Tor Browser 11.256

And I cold reboot the computer 11.633

And the computer reboots Tails 1:34.066

try_for()

try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:454: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/common_steps.rb:453: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/common_steps.rb:453:in `/^the computer (?:re)?boots Tails$/'
features/torified_browsing.feature:157:in `And the computer reboots Tails'

And I enable persistence 0.000

And I log in to a new session 0.000

And all notifications have disappeared 0.000

And I start the Tor Browser in offline mode 0.000

Then the Tor Browser has a bookmark to eff.org 0.000

Hooks

After features/support/hooks.rb:326 5.052

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 04:09:18)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5124/artifact/build-artifacts/04:09:18_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5124/artifact/build-artifacts/04:09:18_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5124/artifact/build-artifacts/04:09:18_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5124/artifact/build-artifacts/04:09:18_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.007