Cucumber Reports (no 44) - Failures Overview

Project	Number	Date
test_Tails_ISO_20268-more-early-patch-functionality	44	16 Apr 2024, 06:24

Feature: Additional software

6:22.543

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:259 0.004

Before features/support/hooks.rb:456 0.005

Steps

Given a computer 0.196

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

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

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

And I accept adding "cowsay" to Additional Software 6.903

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

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

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

And I enable persistence 10.395

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

And I log in to a new session 32.886

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

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

And the network is plugged 0.056

And Tor is ready 18.749

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

And available upgrades have been checked 0.475

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

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

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:464 0.032

After features/support/hooks.rb:305 4.733

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

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22:27_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22:27_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:22: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:89 0.018

Feature: Emergency shutdown

Tags: @product @not_release_blocker

2:11.110

Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4

Hooks

Before features/support/hooks.rb:259 0.005

Steps

Given I have started Tails from DVD without network and logged in 8.505

And I prepare Tails for memory erasure tests 0.407

And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 27.679

And I fill the USB drive with a known pattern 1.274

And I read the content of the test FS 0.059

And patterns cover at least 99% of the test FS size in the guest's memory 2.853

Output 1

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I eject the boot medium 0.293

And I wait for Tails to finish wiping the memory 1:30.038

cannot

cannot find MemoryWipeCompleted.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/erase_memory.rb:229:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'

Then I find very few patterns in the guest's memory 0.000

Hooks

After features/support/hooks.rb:305 9.677

Output 1

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:46:27)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:46:27_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/01:46:27_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

After features/support/hooks.rb:89 0.000

Feature: Tails-related cryptographic keys are up-to-date

Tags: @product

21.300

Scenario The included APT repository keys are up-to-date

Hooks

Before features/support/hooks.rb:259 0.005

Steps

Given I have started Tails from DVD without network and logged in 9.112

Then the keys trusted by APT are valid for the next 3 months 12.187

The

The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'

Hooks

After features/support/hooks.rb:305 4.840

Output 1

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:01:50)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/02:01:50_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/02:01:50_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/02:01:50_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/44/artifact/build-artifacts/02:01:50_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000