Cucumber Reports (no 47) - Failures Overview

Project	Number	Date
test_Tails_ISO_20268-more-early-patch-functionality	47	18 Apr 2024, 22:54

Feature: Additional software

11:4.909

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

Before features/support/hooks.rb:456 0.007

Steps

Given a computer 0.181

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

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 26.103

And I accept adding "cowsay" to Additional Software 7.941

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

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

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

And I enable persistence 13.441

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

And I log in to a new session 35.074

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

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

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

And the network is plugged 0.039

And Tor is ready 22.376

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

And available upgrades have been checked 0.052

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

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/common_steps.rb:591:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:105:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'

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

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

After features/support/hooks.rb:305 8.696

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:26:52)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/47/artifact/build-artifacts/01:26:52_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/47/artifact/build-artifacts/01:26:52_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

After features/support/hooks.rb:89 0.015

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

Tags: @product

20.318

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

Hooks

Before features/support/hooks.rb:259 0.006

Steps

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

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

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

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/47/artifact/build-artifacts/02:09:14_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/47/artifact/build-artifacts/02:09:14_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/47/artifact/build-artifacts/02:09:14_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/47/artifact/build-artifacts/02:09:14_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000