Project Number Date
test_Tails_ISO_stable 6693 26 Sep 2026, 12:16

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
5:14.997
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 12.405
Then I wait until Tor is ready 2.206
And Tor is configured to use the default bridges 0.379
And tca.conf includes no bridge 0.005
And available upgrades have been checked 5:0.000
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:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:40:in `And available upgrades have been checked'
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:339 5.041 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:33:37)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:33:37_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:33:37_Default_Tor_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:33:37_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:33:37_Default_Tor_bridges.journal
After features/support/hooks.rb:108 0.040
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:28.433
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 5.547
And I wait until Tor is ready 0.579
When I disconnect the network through GNOME 10.787
And I connect the network through GNOME 8.997
Then the Tor Connection Assistant autostarts 0.068
And the Tor Connection Assistant connects to Tor 1.447
And I wait until Tor is ready 0.999
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 5:0.006
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:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:80:in `And available upgrades have been checked'
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:339 4.940 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:41:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:41:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:41:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:41:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/00:41:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.052
Feature: Additional software
Tags: @product @check_tor_leaks @slow
16:15.981
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.079
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 16:15.902
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/additional_software_packages.rb:10:in `/^the Additional Software (upgrade|installation) service has started$/'
./features/step_definitions/common_steps.rb:739:in `/^I wait( for a long time)? until Tor is ready$/'
./features/step_definitions/common_steps.rb:707:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:658:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:257: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:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update the APT lists using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 4.775 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 01:29:34)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:29:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:108 0.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:32.224
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.073
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:32.151
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:764:in `/^available upgrades have been checked$/'
./features/step_definitions/common_steps.rb:259: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 installed 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 installed 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:535 0.031
After features/support/hooks.rb:339 4.744 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:36:11)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_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.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_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.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_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.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_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.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_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.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:108 0.005
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
42.405
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.095
And I start Tails from USB drive "__internal" with network unplugged 32.202
And I enable persistence 10.075
And I remove the "cowsay" deb files from the APT cache 0.032
Command 
Command failed: rm /live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb
error code: 1
stdout: 
stderr: rm: cannot remove '/live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb': No such file or directory
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/additional_software_packages.rb:129:in `/^I remove the "([^"]*)" deb files from the APT cache$/'
features/additional_software_packages.feature:124:in `And I remove the "cowsay" deb files from the APT cache'
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
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:535 0.043
After features/support/hooks.rb:339 5.001 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:36:59)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:36:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
37.116
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 37.041
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238: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_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:339 4.778 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:38:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.005
Feature: Upgrading an old Tails USB installation
Tags: @product
45.103
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 45.010
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245: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_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:339 4.819 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:39:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:39:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:39:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:39:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:39:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.005
Feature: Upgrading an old Tails USB installation
Tags: @product
47.235
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 47.162
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245: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_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 5.176 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:42:33)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.005
Feature: Thunderbird email client
6:5.310
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:5.310
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:764:in `/^available upgrades have been checked$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/thunderbird.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I have not configured an email account yet 0.000
And Thunderbird is installed 0.000
When I start Thunderbird 0.000
Then I am prompted to setup an email account 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
0.000
Scenario No add-ons are installed
Steps
Given I cancel setting up an email account 0.000
When I open Thunderbird's Add-ons Manager 0.000
And I open the Extensions tab 0.000
Then I see that no add-ons are enabled in Thunderbird 0.000
And no unexpected connection has leaked from Thunderbird 0.000
After features/support/hooks.rb:535 0.039
After features/support/hooks.rb:339 5.010 
SCENARIO FAILED: 'No add-ons are installed' (at time 03:30:32)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/03:30:32_No_add-ons_are_installed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/03:30:32_No_add-ons_are_installed.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/03:30:32_No_add-ons_are_installed.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/03:30:32_No_add-ons_are_installed.journal
After features/support/hooks.rb:108 0.000
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
20:0.036
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.031
And I re-run tails-upgrade-frontend-wrapper 20:0.004
execution 
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'
<internal:kernel>:187: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:486:in `new'
./features/support/helpers/vm_helper.rb:486:in `execute'
./features/support/helpers/vm_helper.rb:492:in `execute_successfully'
./features/step_definitions/tor.rb:400:in `/^I re-run tails-upgrade-frontend-wrapper$/'
features/tor_stream_isolation.feature:24:in `And I re-run tails-upgrade-frontend-wrapper'
Then I see that tails-upgrade-frontend-wrapper is properly stream isolated 0.000
After features/support/hooks.rb:535 0.047
After features/support/hooks.rb:339 10.729 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 04:08:47)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:08:47_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:08:47_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:08:47_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
3:24.147
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.049
And I start the Tor Browser 7.824
And I open the Tails homepage in the Tor Browser 16.217
Then the Tor Browser loads the Tails homepage 3:0.056
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:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:621:in `/^the Tor Browser loads the (Tails homepage|Tails GitLab)$/'
features/tor_stream_isolation.feature:31:in `Then the Tor Browser loads the Tails homepage'
And I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:535 0.044
After features/support/hooks.rb:339 5.184 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 04:12:31)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:12:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:12:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:12:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/04:12:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000