Project Number Date
test_Tails_ISO_21565-flatpak-safe 68 05 Oct 2026, 16:28

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
1:6.356
Scenario Asking for real bridge settings for the USA in Tor Connection
Steps
Given no bridges are configured in torrc 0.008
When I configure Tor Connection to ask for bridge settings for "United States of America" 6.050
Then some real world bridges are eventually configured in torrc 1:0.297
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: there are no bridge lines in torrc.
<[]> was expected to not be empty.
./features/step_definitions/tor.rb:1293:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/tor.rb:1291:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:1291:in `/^some real world bridges are eventually configured in torrc$/'
features/tor_bridges.feature:118:in `Then some real world bridges are eventually configured in torrc'
After features/support/hooks.rb:339 5.197 
SCENARIO FAILED: 'Asking for real bridge settings for the USA in Tor Connection' (at time 00:32:30)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/00:32:30_Asking_for_real_bridge_settings_for_the_USA_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/00:32:30_Asking_for_real_bridge_settings_for_the_USA_in_Tor_Connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/00:32:30_Asking_for_real_bridge_settings_for_the_USA_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/00:32:30_Asking_for_real_bridge_settings_for_the_USA_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.052
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
2:52.711
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.500
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
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.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.032
And Tor is ready 12.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.567
Given I shutdown Tails and wait for the computer to power off 5.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.683
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 10.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.197
When the network is plugged 0.043
And Tor is ready 10.471
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.840
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 37.991
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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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.799 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:20:19)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.017
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
43.479
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 43.321
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.157
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/thunderbird.rb:113:in `/^the autoconfiguration wizard's choice for the (incoming|outgoing) server is secure (.+)$/'
features/thunderbird.feature:22:in `Then the autoconfiguration wizard's choice for the incoming server is secure IMAP'
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
And the system only established connections with my email server 0.000
After features/support/hooks.rb:535 0.035
After features/support/hooks.rb:339 5.003 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:07:18)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/03:07:18_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/03:07:18_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/03:07:18_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/03:07:18_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:108 0.007