Cucumber Reports (no 11) - Failures Overview

Project	Number	Date
test_Tails_ISO_test-snapshot-restore-improvements	11	24 Aug 2026, 13:09

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

21.549

Scenario Upgrading an initial Tails installation with an incremental upgrade

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 with a persistent partition enabled and logged in 5.149

And no SquashFS delta is installed 0.094

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.172

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342

When the network is plugged 0.026

And Tor is ready 15.505

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/step_definitions/common_steps.rb:672:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000

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

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000

Then Tails is running version 6.2~testoverlayfs 0.000

And all tps features are active 0.000

And the file system changes introduced in version 6.2~testoverlayfs are present 0.000

And only the 6.2~testoverlayfs SquashFS delta is installed 0.000

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.000

# 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.000

When the network is plugged 0.000

And Tor is ready 0.000

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000

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

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000

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

Hooks

After features/support/hooks.rb:339 4.965

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/01:16:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:108 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

20:4.682

Scenario Outline Tails is localized for every tier-1 language

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 stopped at Tails Greeter's login screen 4.581

And I set an administration password 20:0.101

execution

execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
<internal:kernel>:187:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:89:in `new'
./features/support/helpers/dogtail.rb:89: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:360:in `click'
./features/step_definitions/common_steps.rb:566:in `open_greeter_additional_settings'
./features/step_definitions/common_steps.rb:593:in `/^I set an administration password$/'
features/localization.feature:52:in `And I set an administration password'
features/localization.feature:23:in `And I set an administration password'

When I log in to a new session in Indonesian (id) 0.000

Then the keyboard layout is set to "id" 0.000

And tpsd is localized to the selected locale 0.000

Given the network is plugged 0.000

And Tor is ready 0.000

Then I successfully start the Unsafe Browser 0.000

And I kill the Unsafe Browser 0.000

Given Thunderbird is installed 0.000

When I enable the screen keyboard 0.000

Then the screen keyboard works in Tor Browser 0.000

And DuckDuckGo is the default search engine 0.000

And I kill the Tor Browser 0.000

And the screen keyboard works in Thunderbird 0.000

And the layout of the screen keyboard is set to "us" 0.000

Hooks

After features/support/hooks.rb:339 10.846

Output 1

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 02:16:02)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:16:02_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:16:02_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:16:02_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal

After features/support/hooks.rb:108 0.000

Feature: Localization

Tags: @product

20.259

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.004

Steps

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

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

Then Tails is running from USB drive "__internal" 0.285

And I create a persistent partition 13.611

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.263

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:29:37_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/11/artifact/build-artifacts/02:29:37_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:29:37_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:29:37_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.journal

After features/support/hooks.rb:108 0.000

Feature: Tails persistence

Tags: @product

3:8.280

Scenario Booting Tails from a USB drive with a disabled persistent partition

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 with a persistent partition and stopped at Tails Greeter's login screen 6.411

When I log in to a new session without activating the Persistent Storage 3:1.869

cannot

cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:617:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:558:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:14:in `When I log in to a new session without activating the Persistent Storage'

Then Tails is running from USB drive "__internal" 0.000

And persistence is disabled 0.000

But a Tails persistence partition exists on USB drive "__internal" 0.000

Hooks

After features/support/hooks.rb:339 5.078

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 02:39:56)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:39:56_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:39:56_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:39:56_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:39:56_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal

After features/support/hooks.rb:108 0.000

Feature: Tails persistence

Tags: @product

18.303

Scenario Deleting data of a Persistent Storage feature

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Steps

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

Then persistence for "Persistent" is active 0.126

When I create a file in the Persistent directory 0.060

And I disable the first tps feature 2.541

And I delete the data of the Persistent Folder feature 10.254

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/usb.rb:1761:in `/^I delete the data of the Persistent Folder feature$/'
features/persistence.feature:69:in `And I delete the data of the Persistent Folder feature'

Then the file I created does not exist on the Persistent Storage 0.000

Hooks

After features/support/hooks.rb:339 5.347

Output 1

SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 02:44:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:44:29_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:44:29_Deleting_data_of_a_Persistent_Storage_feature.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:44:29_Deleting_data_of_a_Persistent_Storage_feature.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:44:29_Deleting_data_of_a_Persistent_Storage_feature.journal

After features/support/hooks.rb:108 0.000

Feature: Tails persistence

Tags: @product

17.222

Scenario Changing the Persistent Storage passphrase

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Steps

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

# Note that if anything fails after the passphrase was changed and

# before it's changed back below, subsequent scenarios might fail

# because the Persistent Storage doesn't have the expected passphrase.

When I change the passphrase of the Persistent Storage 11.385

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/usb.rb:484:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:128:in `When I change the passphrase of the Persistent Storage'

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

Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000

And I change the passphrase of the Persistent Storage back to the original 0.000

Hooks

After features/support/hooks.rb:339 5.359

Output 1

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 02:50:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:50:49_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:50:49_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:50:49_Changing_the_Persistent_Storage_passphrase.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/02:50:49_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:108 0.000

Feature: Using persistent Tor bridges and pluggable transports

20.017

Background

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Steps

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

And I create a persistent partition with the default settings 13.664

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/persistent_tor_bridges.feature:9:in `And I create a persistent partition with the default settings'

Then the "TorConfiguration" tps feature is not enabled 0.000

When the network is plugged 0.000

And the Tor Connection Assistant autostarts 0.000

And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000

And I wait until Tor is ready 0.000

Then tca.conf includes the configured bridges 0.000

And the "TorConfiguration" tps feature is enabled and active 0.000

When I cold reboot the computer 0.000

And the computer reboots Tails 0.000

And I enable persistence 0.000

And I capture all network traffic 0.000

And I log in to a new session 0.000

Then tca.conf includes the configured bridges 0.000

When the network is plugged 0.000

And the Tor Connection Assistant autostarts 0.000

Feature: Using persistent Tor bridges and pluggable transports

Tags: @product

0.000

Scenario Using Persistent Tor bridges

Steps

When I choose to connect to Tor automatically 0.000

And I accept Tor Connection's offer to use my persistent bridges 0.000

And I click "Connect to Tor" 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes the configured bridges 0.000

And the "TorConfiguration" tps feature is enabled and active 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:339 5.169

Output 1

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 03:01:15)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:01:15_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:01:15_Using_Persistent_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:01:15_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:01:15_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:108 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

33.326

Scenario The Tor Browser's circuit view feature works as expected

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 and logged in and the network is connected 6.797

When I start the Tor Browser 26.528

cannot

cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:517:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:507:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:88:in `When I start the Tor Browser'

And I open the Tails homepage in the Tor Browser 0.000

Then the Tor Browser loads the Tails homepage 0.000

And Tor Browser's circuit view is working 0.000

Hooks

After features/support/hooks.rb:339 5.300

Output 1

SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 03:21:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:21:48_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:21:48_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:21:48_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/11/artifact/build-artifacts/03:21:48_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:108 0.000