Project Number Date
test_Tails_ISO_stable 6692 25 Sep 2026, 12:12

Failures Overview

The following summary displays scenarios that failed.

27.487
Scenario Changing locale after installing a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Before features/support/hooks.rb:527 0.002
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 11.477
When I start GNOME Software 1.292
And I install Thunderbird using GNOME Software 14.717
The
The Dogtail init script raised: SearchError: descendant of [application | gnome-software]: child with name='Thunderbird' roleName='label'
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/flatpak.rb:25:in `/^I install (.*) using GNOME Software$/'
features/flatpak.feature:40:in `And I install Thunderbird using GNOME Software'
Then the org.mozilla.thunderbird Flatpak is installed after at most 600 seconds 0.000
And the "de" locale is not present in the org.mozilla.thunderbird.Locale Flatpak extension 0.000
Given I set Tails to boot with options "flatpak" 0.000
When I cold reboot the computer 0.000
Then the computer boots Tails 0.000
When I enable persistence 0.000
And I log in to a new session in German (de) 0.000
Given it has been 3 days since GNOME Software checked for updates 0.000
And GNOME Software thinks it is after 06:00 but before 23:00 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the "de" locale is present in the org.mozilla.thunderbird.Locale Flatpak extension after at most 600 seconds 0.000
After features/support/hooks.rb:535 0.044
After features/support/hooks.rb:339 4.969

SCENARIO FAILED: 'Changing locale after installing a Flatpak' (at time 00:13:56)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:13:56_Changing_locale_after_installing_a_Flatpak.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:13:56_Changing_locale_after_installing_a_Flatpak.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:13:56_Changing_locale_after_installing_a_Flatpak.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:13:56_Changing_locale_after_installing_a_Flatpak.journal

After features/support/hooks.rb:108 0.002
Tags: @product
5:30.710
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 29.856
Then I wait until Tor is ready 0.848
And tca.conf includes the configured bridges 0.005
And available upgrades have been checked 5:0.000
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:31:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:339 4.711

SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:29:18)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:29:18_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:29:18_Using_obfs4_pluggable_transports_from_a_QR_code.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:29:18_Using_obfs4_pluggable_transports_from_a_QR_code.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:29:18_Using_obfs4_pluggable_transports_from_a_QR_code.journal

After features/support/hooks.rb:108 0.036
5:14.944
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 13.746
Then I wait until Tor is ready 0.865
And Tor is configured to use the default bridges 0.328
And tca.conf includes no bridge 0.004
And available upgrades have been checked 5:0.000
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 4.935

SCENARIO FAILED: 'Default Tor bridges' (at time 00:34:46)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:34:46_Default_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:34:46_Default_Tor_bridges.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:34:46_Default_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:34:46_Default_Tor_bridges.journal

After features/support/hooks.rb:108 0.043
Tags: @product
5:12.929
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.192
When I configure Tor Connection to ask for bridge settings based on my location 5.782
And I wait until Tor is ready 6.954
And available upgrades have been checked 5:0.000
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:105:in `And available upgrades have been checked'
Then 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 4.922

SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:15)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:44:15_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:44:15_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:44:15_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/00:44:15_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal

After features/support/hooks.rb:108 0.033
6:38.090
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.010
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.108
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:37.982
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.030
After features/support/hooks.rb:339 5.098

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:20:17)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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/6692/artifact/build-artifacts/01:20:17_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.010
6:36.663
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.001
Steps
Given a computer 0.114
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:36.549
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.036
After features/support/hooks.rb:339 4.881

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

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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/6692/artifact/build-artifacts/01:26:59_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
43.685
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.090
And I start Tails from USB drive "__internal" with network unplugged 32.349
And I enable persistence 11.199
And I remove the "cowsay" deb files from the APT cache 0.045
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.033
After features/support/hooks.rb:339 5.181

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:27:48)

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/6692/artifact/build-artifacts/01:27:48_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/6692/artifact/build-artifacts/01:27:48_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/6692/artifact/build-artifacts/01:27:48_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/6692/artifact/build-artifacts/01:27:48_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/6692/artifact/build-artifacts/01:27:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:27:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:27:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:27:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:108 0.005
9:38.378
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.347
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.022
And Tor is ready 12.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.958
Given I shutdown Tails and wait for the computer to power off 7.776
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.931
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.199
When the network is plugged 0.032
And Tor is ready 10.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4:10.078
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.569
Given I shutdown Tails and wait for the computer to power off 3.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.926
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.663
And the file system changes introduced in version 6.3~testoverlayfs are present 0.261
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.030
And Tor is ready 10.036
Then the Upgrader considers the system as up-to-date 2:0.002
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.811

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:44:57)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:44:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:108 0.010
5:25.114
Scenario Tails shuts down on DVD boot medium removal
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 5:25.114
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\ and\ the\ network\ is\ connected$/'
features/emergency_shutdown.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
When I eject the boot medium 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:339 4.704

SCENARIO FAILED: 'Tails shuts down on DVD boot medium removal' (at time 01:50:51)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:50:51_Tails_shuts_down_on_DVD_boot_medium_removal.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:50:51_Tails_shuts_down_on_DVD_boot_medium_removal.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:50:51_Tails_shuts_down_on_DVD_boot_medium_removal.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/01:50:51_Tails_shuts_down_on_DVD_boot_medium_removal.journal

After features/support/hooks.rb:108 0.000
5:22.235
Scenario The Tails documentation launcher works when online
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 5:22.235
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\ and\ the\ network\ is\ connected$/'
features/documentation.feature:11:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start "Tails Documentation" via GNOME Activities Overview 0.000
Then the Tor Browser has started 0.000
And "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:339 4.616

SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 02:04:21)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/02:04:21_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/02:04:21_The_Tails_documentation_launcher_works_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/02:04:21_The_Tails_documentation_launcher_works_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/02:04:21_The_Tails_documentation_launcher_works_when_online.journal

After features/support/hooks.rb:108 0.000
8:0.439
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 43.476
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.171
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.278
When I accept the autoconfiguration wizard's configuration 27.326
And I send an email to myself 5.590
And I fetch my email 1.393
Then I can find the email I sent to myself in my inbox 6:42.202
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'
<internal:kernel>:187: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:27:in `Then I can find the email I sent to myself in my inbox'
And the system only established connections with my email server 0.000
After features/support/hooks.rb:535 0.037
After features/support/hooks.rb:339 5.123

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

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/03:45:25_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/03:45:25_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/03:45:25_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6692/artifact/build-artifacts/03:45:25_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:108 0.007