Project Number Date
test_Tails_ISO_21790-tor-0.4.9.13 1 24 Sep 2026, 16:49

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
5:25.021
Scenario Installing, starting and uninstalling a Flatpak
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 I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 5:25.021
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\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/flatpak.feature:25:in `Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected'
When I start GNOME Software 0.000
And I install Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 0.000
When I start the org.signal.Signal Flatpak 0.000
Then the org.signal.Signal Flatpak is running 0.000
Given I kill the org.signal.Signal Flatpak 0.000
And I go to the main screen of GNOME Software 0.000
When I uninstall Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.042
After features/support/hooks.rb:339 4.964 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:13:31)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:13:31_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:13:31_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:13:31_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:13:31_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.003
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
5:12.842
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 11.496
Then I wait until Tor is ready 1.043
And Tor is configured to use the default bridges 0.296
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 6.099 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:37:22)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:37:22_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:37:22_Default_Tor_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:37:22_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:37:22_Default_Tor_bridges.journal
After features/support/hooks.rb:108 0.062
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:24.418
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.870
And I wait until Tor is ready 0.512
When I disconnect the network through GNOME 9.607
And I connect the network through GNOME 7.173
Then the Tor Connection Assistant autostarts 0.067
And the Tor Connection Assistant connects to Tor 0.173
And I wait until Tor is ready 1.011
And Tor is using the same configuration as before 0.000
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: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.868 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:44:43)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:44:43_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:44:43_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:44:43_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/00:44:43_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.056
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker @fragile @doc
6:8.149
Scenario I am warned I can not use Additional Software when I start Tails from a DVD and install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:8.149
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/additional_software_packages.feature:15:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update the APT lists using apt 0.000
When I install "popularity-contest" using apt 0.000
Then I am notified I can not use Additional Software for "popularity-contest" 0.000
And I can open the Additional Software documentation from the notification 0.000
After features/support/hooks.rb:535 0.042
After features/support/hooks.rb:339 4.941 
SCENARIO FAILED: 'I am warned I can not use Additional Software when I start Tails from a DVD and install a package' (at time 01:18:17)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:18:17_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.journal
After features/support/hooks.rb:108 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:7.713
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.080
And I start Tails from USB drive "__internal" and I login with an administration password 6:7.632
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:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update the APT lists using apt 0.000
When I install "ripgrep" using apt 0.000
Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 0.000
And the package "ripgrep" is installed 0.000
After features/support/hooks.rb:535 0.054
After features/support/hooks.rb:339 5.115 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:27:13)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:27:13_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:108 0.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:40.966
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.002
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.083
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:40.882
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: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.034
After features/support/hooks.rb:339 5.141 
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:34:00)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:34:00_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.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
8:23.138
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.002
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.082
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:40.451
And I configure APT to prefer an old version of cowsay 0.004
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 8.086
And I accept adding "cowsay" to Additional Software 2.349
And Additional Software is correctly configured for package "cowsay" 0.674
And I shutdown Tails and wait for the computer to power off 12.852
And I start Tails from USB drive "__internal" with network unplugged 35.489
And I enable persistence 12.900
# 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.009
# 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.055
And I log in to a new session 8.624
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.238
And I revert the APT tweaks that made it prefer an old version of cowsay 0.035
# 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.047
And the network is plugged 0.034
And Tor is ready 11.202
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/additional_software_packages.feature:101:in `And available upgrades have been checked'
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.032
After features/support/hooks.rb:339 4.978 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:42:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:42:28_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.012
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
5:34.745
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.278
And no SquashFS delta is installed 0.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.031
And Tor is ready 12.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.864
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.359
Given I shutdown Tails and wait for the computer to power off 6.926
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.212
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.667
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.033
And Tor is ready 11.123
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.904
Given I shutdown Tails and wait for the computer to power off 3.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.007
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.028
And Tor is ready 10.522
Then the Upgrader considers the system as up-to-date 2: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/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:339 4.838 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:57:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/01:57:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.012
Feature: Getting a DHCP lease without leaking too much information
5:23.156
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in 6.536
And I capture all network traffic 0.003
And the network is plugged 0.052
And Tor is ready 9.961
And all notifications have disappeared 6.601
And available upgrades have been checked 5:0.001
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/dhcp.feature:14:in `And available upgrades have been checked'
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.000
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:339 4.828 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 02:11:18)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/02:11:18_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/02:11:18_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/02:11:18_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/02:11:18_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:108 0.048
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
3:21.016
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.041
And I start the Tor Browser 8.155
And I open the Tails homepage in the Tor Browser 12.758
Then the Tor Browser loads the Tails homepage 3:0.062
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.033
After features/support/hooks.rb:339 4.930 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 04:09:40)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:09:40_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_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:09:40_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:09:40_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:09:40_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
3:23.314
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.296
When I start the Tor Browser 7.017
And I open the Tails homepage in the Tor Browser 6.910
Then the Tor Browser loads the Tails homepage 3:0.089
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/torified_browsing.feature:90:in `Then the Tor Browser loads the Tails homepage'
And Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:339 5.424 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 04:18:09)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:18:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:18:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:18:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:18:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
5:17.485
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.891
And the network is plugged 0.025
And I successfully configure Tor 9.566
And available upgrades have been checked 5:0.001
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/torified_browsing.feature:105:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:339 4.880 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:24:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:24:02_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:24:02_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:24:02_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/1/artifact/build-artifacts/04:24:02_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000