Cucumber Reports (no 4971) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4971	24 Jul 2024, 22:31

Feature: Additional software

7:34.255

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

Steps

Given a computer 0.198

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

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

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

And I accept adding "cowsay" to Additional Software 5.598

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

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

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

And I enable persistence 12.016

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

And I log in to a new session 39.252

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

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

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

And Tor is ready 20.148

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

And available upgrades have been checked 0.770

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

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

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

After features/support/hooks.rb:326 6.175

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:19:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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/4971/artifact/build-artifacts/01:19:59_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.016

Feature: Tails persistence

Tags: @product

22:32.187

Scenario Creating and using a persistent NetworkManager connection

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

And the network is plugged 0.039

And Tor is ready 16.898

And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.190

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

Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:56.033

execution

execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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/common_steps.rb:706:in `new'
./features/step_definitions/common_steps.rb:706:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:292:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/persistence.feature:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

And I capture all network traffic 0.000

And the network is plugged 0.000

And Tor is ready 0.000

And I switch to the "persistent-con-current" NetworkManager connection 0.000

And the 1st network device has a spoofed MAC address configured 0.000

And no network device leaked the real MAC address 0.000

Hooks

After features/support/hooks.rb:326 10.841

Output 1

SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 03:17:53)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4971/artifact/build-artifacts/03:17:53_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4971/artifact/build-artifacts/03:17:53_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4971/artifact/build-artifacts/03:17:53_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.009