Project Number Date
test_Tails_ISO_stable 4846 17 May 2024, 12:12

Failures Overview

The following summary displays scenarios that failed.

6:56.601
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.007
Before features/support/hooks.rb:456 0.006
Steps
Given a computer 0.172
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:19.998
And I configure APT to prefer an old version of cowsay 0.024
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.436
And I accept adding "cowsay" to Additional Software 5.701
And Additional Software is correctly configured for package "cowsay" 0.879
And I shutdown Tails and wait for the computer to power off 6.360
And I start Tails from USB drive "__internal" with network unplugged 58.834
And I enable persistence 16.491
# 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.026
And I log in to a new session 36.845
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.352
And I revert the APT tweaks that made it prefer an old version of cowsay 0.071
# 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.060
And the network is plugged 0.031
And Tor is ready 20.924
# 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.717
And available upgrades have been checked 0.495
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.113
And I can open the Additional Software configuration window from the notification 31.065
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
After features/support/hooks.rb:464 0.029
After features/support/hooks.rb:305 4.908

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:26:12)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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/4846/artifact/build-artifacts/01:26:12_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_stable/4846/artifact/build-artifacts/01:26:12_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_stable/4846/artifact/build-artifacts/01:26:12_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.017
Tags: @product
21.314
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.173
Then the keys trusted by APT are valid for the next 3 months 13.141
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.467

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/02:11:06_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/02:11:06_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/02:11:06_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/02:11:06_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000
53.463
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 10.694
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.387
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.356
When I accept the autoconfiguration wizard's configuration 18.828
And I send an email to myself 23.196
The
The Dogtail init script raised: SearchError: descendent of [application | Thunderbird]: child with name="Write: Automated test suite: QkSEB4ioko38DzqtMhnkogM3R6l1HSPi - Thunderbird"
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/thunderbird.rb:178:in `/^I send an email to myself$/'
features/thunderbird.feature:23:in `And I send an email to myself'
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:464 0.035
After features/support/hooks.rb:305 4.410

SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:40:23)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/03:40:23_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/03:40:23_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/03:40:23_I_can_send_emails,_and_receive_emails_over_IMAP.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4846/artifact/build-artifacts/03:40:23_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:89 0.000