Cucumber Reports (no 10) - Failures Overview

Project	Number	Date
test_Tails_ISO_test-snapshot-restore-improvements	10	24 Aug 2026, 12:04

Feature: Time syncing

Tags: @product @check_tor_leaks

18.738

Scenario Clock is one day in the future while using obfs4 bridges

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Before features/support/hooks.rb:527 0.002

Steps

Given I have started Tails from DVD without network and logged in 3.461

When I bump the system time with "+1 day" 0.152

And I capture all network traffic 0.003

And the network is plugged 0.034

And the Tor Connection Assistant autostarts 4.827

And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 10.259

The

The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
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/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:670:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:27:in `And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode'

And I wait until Tor is ready 0.000

Then the system clock is less than 5 minutes incorrect 0.000

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:535 0.032

After features/support/hooks.rb:339 5.162

Output 1

SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:14:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:14:29_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:14:29_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:14:29_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:14:29_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal

After features/support/hooks.rb:108 0.061

Feature: Using Tor bridges and pluggable transports

Tags: @product

11.331

Scenario TCA can reconnect after a connection failure

Steps

Given the Tor network and default bridges are blocked 0.961

When I unsuccessfully configure a direct connection in the Tor Connection Assistant 10.369

Expected

Expected TCAConnectionFailure to be raised but got Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (RuntimeError)
./features/step_definitions/tor.rb:795:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:790:in `/^I unsuccessfully configure (a direct connection|some .* bridges) in the Tor Connection Assistant$/'
features/tor_bridges.feature:55:in `When I unsuccessfully configure a direct connection in the Tor Connection Assistant'

Then the Tor Connection Assistant reports that it failed to connect 0.000

And tca.conf is empty 0.000

Given the Tor network and default bridges are unblocked 0.000

When I retry connecting to Tor 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes no bridge 0.000

And available upgrades have been checked 0.000

And all Internet traffic has only flowed through Tor or connectivity check service 0.000

Hooks

After features/support/hooks.rb:339 4.866

Output 1

SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:21:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:21:34_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:21:34_TCA_can_reconnect_after_a_connection_failure.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:21:34_TCA_can_reconnect_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:21:34_TCA_can_reconnect_after_a_connection_failure.journal

After features/support/hooks.rb:108 0.047

Feature: Installing Tails to a USB drive

Tags: @product

34.205

Scenario Re-installing Tails over an existing USB installation with a persistent partition

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.

# This first part is done without Tails Installer (install from Tails USB image)

# Note: the "__internal" disk will keep its state across scenarios

# and features until one of its snapshots is restored.

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.257

And I have started Tails from DVD without network and logged in 3.631

And I clone USB drive "__internal" to a temporary USB drive "install" 0.793

And I plug USB drive "install" 2.196

# This second part is done with Tails Installer, that's what this scenario is about

When I reinstall Tails to USB drive "install" by cloning 22.326

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:1031:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/usb.rb:155:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:195:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_install.feature:75:in `When I reinstall Tails to USB drive "install" by cloning'

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is no persistence partition on USB drive "install" 0.000

Hooks

After features/support/hooks.rb:339 5.245

Output 1

SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 00:48:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:48:16_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:48:16_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:48:16_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/00:48:16_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal

After features/support/hooks.rb:108 0.131

Feature: Using Evince

Tags: @product

25.922

Scenario I can view and print a PDF file stored in non-persistent /home/amnesia

Hooks

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 3.671

And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia" as user "amnesia" 0.060

When I open "/home/amnesia/default-testpage.pdf" with Evince 22.189

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:1031:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/evince.rb:2:in `/^I open "([^"]+)" with Evince$/'
features/evince.feature:15:in `When I open "/home/amnesia/default-testpage.pdf" with Evince'

Then I see "CupsTestPage.png" after at most 40 seconds 0.000

And I can print the current document to "/home/amnesia/output.pdf" 0.000

Hooks

After features/support/hooks.rb:339 5.103

Output 1

SCENARIO FAILED: 'I can view and print a PDF file stored in non-persistent /home/amnesia' (at time 01:25:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:25:42_I_can_view_and_print_a_PDF_file_stored_in_non-persistent__home_amnesia.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:25:42_I_can_view_and_print_a_PDF_file_stored_in_non-persistent__home_amnesia.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:25:42_I_can_view_and_print_a_PDF_file_stored_in_non-persistent__home_amnesia.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:25:42_I_can_view_and_print_a_PDF_file_stored_in_non-persistent__home_amnesia.journal

After features/support/hooks.rb:108 0.000

Feature: Hardware failures

Tags: @product

1:1.670

Scenario Outline Disk partitioning errors without a persistent partition

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

Given a computer 0.094

And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000

And I temporarily create a 7200 MiB disk named "temp" 0.022

And I plug USB drive "temp" 1.034

And I write the Tails USB image to disk "temp" 14.004

When I start Tails from USB drive "temp" with network unplugged 46.513

Known

Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:252: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/hardware_failure.feature:82:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'

Then Tails is running from USB drive "temp" 0.000

And the Greeter recommends reinstalling Tails due to partitioning errors 0.000

And the Greeter forbids starting Tails 0.000

And the Greeter forbids all settings but language 0.000

And Tails detected partitioning error fs-not-resized 0.000

Hooks

After features/support/hooks.rb:339 4.750

Output 1

SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 01:38:57)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:38:57_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:38:57_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:38:57_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/01:38:57_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal

After features/support/hooks.rb:108 0.122

Feature: Localization

Tags: @product

19.736

Scenario Cleartext localization preferences have priority over Persistent Storage

Hooks

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 without a persistent partition and logged in 5.865

# The first boot simulates a legacy Tails, where locale is only saved in Persistent Storage

Then Tails is running from USB drive "__internal" 0.302

And I create a persistent partition 13.568

The

The Dogtail init script raised: SearchError: descendant of [frame | Persistent Storage]: 'Create Persistent Storage' button
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:272:in `button'
./features/step_definitions/usb.rb:386:in `/^I try to create a persistent partition( for Additional Software)?( using the wizard that was already open)?$/'
./features/step_definitions/usb.rb:355:in `/^I create a persistent partition( with the default settings)?( for Additional Software)?( using the wizard that was already open)?$/'
features/localization.feature:86:in `And I create a persistent partition'

And I manually store legacy localization settings in Persistent Storage 0.000

When I shutdown Tails and wait for the computer to power off 0.000

# The second boot verifies that the legacy setting still works

And I start Tails from USB drive "__internal" with network unplugged 0.000

Then the Welcome Screen's language is set to English 0.000

And the Welcome Screen's formats is set to United States 0.000

When I enable persistence 0.000

Then the Welcome Screen's language is set to German 0.000

And the Welcome Screen's formats is set to France 0.000

When I set the language to Italian (it) 0.000

Then the language and keyboard have not been saved in cleartext storage 0.000

When I save the language and keyboard options in cleartext storage 0.000

Then the "it" language and keyboard have been saved in cleartext storage 0.000

And I shutdown Tails and wait for the computer to power off 0.000

# The third boot verifies that cleartext has priority

And I start Tails from USB drive "__internal" with network unplugged 0.000

Then the Welcome Screen's language is set to Italian 0.000

And the Welcome Screen's formats is set to Italy 0.000

When I enable persistence 0.000

# Only formats are loaded from persistence

Then the Welcome Screen's formats is set to France 0.000

And the Welcome Screen's language is set to Italian 0.000

Hooks

After features/support/hooks.rb:339 5.275

Output 1

SCENARIO FAILED: 'Cleartext localization preferences have priority over Persistent Storage' (at time 02:09:24)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:09:24_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:09:24_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:09:24_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:09:24_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.journal

After features/support/hooks.rb:108 0.000

Feature: The Tor enforcement is effective

Tags: @product

18.298

Scenario The system DNS is always set up to use Tor's DNSPort

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.008

Steps

Given I have started Tails from DVD without network and logged in 3.869

And the system DNS is using the local DNS resolver 0.006

And the network is plugged 0.045

And I successfully configure Tor 14.376

The

The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
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/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:718:in `/^I successfully configure Tor$/'
features/tor_enforcement.feature:63:in `And I successfully configure Tor'

Then the system DNS is still using the local DNS resolver 0.000

Hooks

After features/support/hooks.rb:339 5.203

Output 1

SCENARIO FAILED: 'The system DNS is always set up to use Tor's DNSPort' (at time 02:55:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:55:31_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:55:31_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:55:31_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/02:55:31_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.journal

After features/support/hooks.rb:108 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

19.024

Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 8.319

And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 10.705

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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/veracrypt.rb:164:in `/^I unlock and mount this VeraCrypt (volume|file container) with Unlock VeraCrypt Volumes$/'
features/veracrypt.feature:32:in `And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes'

And I open this VeraCrypt volume in GNOME Files 0.000

Then I see the expected contents in this VeraCrypt volume 0.000

When I lock the currently opened VeraCrypt file container 0.000

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:339 4.950

Output 1

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 03:18:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/03:18:04_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/03:18:04_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/03:18:04_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/10/artifact/build-artifacts/03:18:04_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:108 0.000