Project Number Date
test_Tails_ISO_devel 3352 16 Apr 2024, 21:46

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
13:3.575
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:259 0.006
Before features/support/hooks.rb:456 0.009
Steps
Given a computer 0.201
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:17.322
And I configure APT to prefer an old version of cowsay 0.026
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 27.266
And I accept adding "cowsay" to Additional Software 4.881
And Additional Software is correctly configured for package "cowsay" 0.858
And I shutdown Tails and wait for the computer to power off 6.466
And I start Tails from USB drive "__internal" with network unplugged 1:0.206
And I enable persistence 13.269
# 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.030
And I log in to a new session 36.855
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.855
And I revert the APT tweaks that made it prefer an old version of cowsay 0.061
# 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.072
And the network is plugged 0.044
And Tor is ready 19.117
# 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 8.260
And available upgrades have been checked 0.098
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.137
And I can open the Additional Software configuration window from the notification 3.910
And I shutdown Tails and wait for the computer to power off 2:2.755
And I start Tails from USB drive "__internal" with network unplugged 57.528
And I enable persistence 18.536
# 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 27.591
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:13.523
And I revert the APT tweaks that made it prefer an old version of cowsay 0.046
And the network is plugged 0.052
And Tor is ready 1:1.575
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:644:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:599:in `/^Tor is ready$/'
features/additional_software_packages.feature:117:in `And Tor is ready'
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.034
After features/support/hooks.rb:305 20:3.570
Error message 
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:124:in `execute'
./features/support/helpers/remote_shell.rb:135:in `initialize'
./features/support/helpers/vm_helper.rb:445:in `new'
./features/support/helpers/vm_helper.rb:445:in `execute'
./features/support/helpers/misc_helpers.rb:246:in `block in save_tor_journal'
./features/support/helpers/misc_helpers.rb:245:in `open'
./features/support/helpers/misc_helpers.rb:245:in `save_tor_journal'
./features/support/hooks.rb:342:in `After'
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:33:30)
After features/support/hooks.rb:89 0.036
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
21.935
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.009
Steps
Given I have started Tails from DVD without network and logged in 8.480
Then the keys trusted by APT are valid for the next 3 months 13.454
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'
After features/support/hooks.rb:305 4.347 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:34:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3352/artifact/build-artifacts/02:34:03_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3352/artifact/build-artifacts/02:34:03_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3352/artifact/build-artifacts/02:34:03_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3352/artifact/build-artifacts/02:34:03_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000