Project Number Date
test_Tails_ISO_tca-misc-improvements 4 11 Apr 2025, 18:22

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product
1:43.527
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.147
And I start Tails from USB drive "usbimage" with network unplugged and I login 1:43.380
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/usb_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:330 4.921 
SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 00:59:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/00:59:04_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/00:59:04_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/00:59:04_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/00:59:04_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.journal
After features/support/hooks.rb:100 0.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:2.128
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:511 0.004
Steps
Given a computer 0.189
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:1.938
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:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:300: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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 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
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 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
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
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
After features/support/hooks.rb:519 0.044
After features/support/hooks.rb:330 14.207 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:18:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/01:18:54_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/01:18:54_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_tca-misc-improvements/4/artifact/build-artifacts/01:18:54_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_tca-misc-improvements/4/artifact/build-artifacts/01:18:54_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.048
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
6:56.210
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:511 0.004
Steps
Given a computer 0.178
And I start Tails from USB drive "__internal" with network unplugged 1:0.702
And I enable persistence 12.382
And I remove the "cowsay" deb files from the APT cache 0.065
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.094
And I log in to a new session 40.799
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.988
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:599:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:519 0.036
After features/support/hooks.rb:330 9.124 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:26:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/01:26:04_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/01:26:04_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/01:26:04_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
24:1.670
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 11.351
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.327
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.344
When I accept the autoconfiguration wizard's configuration 18.891
And I send an email to myself 6.257
And I fetch my email 1.394
Then I can find the email I sent to myself in my inbox 23:23.102
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/thunderbird.rb:190:in `/^I can find the email I sent to myself in my inbox$/'
features/thunderbird.feature:25:in `Then I can find the email I sent to myself in my inbox'
After features/support/hooks.rb:519 0.029
After features/support/hooks.rb:330 5.707 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 04:24:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:24:10_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:24:10_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:24:10_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:24:10_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
3:33.048
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.053
When I start the Tor Browser 20.864
And the Tor Browser loads the startup page 3:0.129
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:502:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:92:in `And the Tor Browser loads the startup page'
Then Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:330 5.480 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 04:43:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:43:29_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:43:29_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:43:29_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/4/artifact/build-artifacts/04:43:29_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000