Project Number Date
test_Tails_ISO_feature-arti 96 23 Jun 2025, 19:31

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
6:14.694
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Before features/support/hooks.rb:509 0.008
Steps
Given I have started Tails from DVD without network and logged in 1:12.281
When the network is plugged 1.709
And the Tor Connection Assistant autostarts 5.863
And I configure some normal bridges in the Tor Connection Assistant 23.963
And I wait until Tor is ready 4:30.876
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:18:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.043
After features/support/hooks.rb:330 5.923 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:27:32)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:27:32_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
6:0.192
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 1:5.676
When I bump the system time with "+1 day" 1.649
And I capture all network traffic 0.060
And the network is plugged 0.373
And the Tor Connection Assistant autostarts 5.925
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.695
And I wait until Tor is ready 4:30.810
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:28:in `And I wait until Tor is ready'
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
After features/support/hooks.rb:517 0.029
After features/support/hooks.rb:330 6.495 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:33:38)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:33:38_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:33:38_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_feature-arti/96/artifact/build-artifacts/00:33:38_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:33:38_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:33:38_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:33:38_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.047
Feature: Time syncing
Tags: @product @check_tor_leaks
5:28.840
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.203
When I bump the system time with "+8 hours +15 minutes" 0.341
And all notifications have disappeared 4.332
And I capture all network traffic 0.025
And I make sure time sync before Tor connects fails 0.329
And the network is plugged 0.224
And the Tor Connection Assistant autostarts 4.785
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 6.053
And I click "Connect to Tor" 1.155
And the Tor Connection Assistant fails to connect to Tor 15.290
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 15.111
Then the system clock is less than 20 minutes incorrect 0.478
When I click "Connect to Tor" 1.274
Then I wait until Tor is ready 4:30.234
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:77:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.033
After features/support/hooks.rb:330 6.502 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:44:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:44:18_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:100 0.075
Feature: Time syncing
Tags: @product @check_tor_leaks
5:26.304
Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.005
Steps
Given I have started Tails from DVD without network and logged in 10.499
When I bump the system time with "+8 hours +15 minutes" 0.204
And all notifications have disappeared 4.174
And I capture all network traffic 0.003
And the network is plugged 0.116
And the Tor Connection Assistant autostarts 5.387
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 5.114
And I click "Connect to Tor" 1.263
Then the Tor Connection Assistant reports that it failed to connect 11.997
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 15.264
Then the system clock is less than 20 minutes incorrect 0.415
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.520
When I click "Connect to Tor" 1.151
Then I wait until Tor is ready 4:30.189
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:99:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:517 0.036
After features/support/hooks.rb:330 5.493 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:49:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:49:51_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.347
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 12.526
Then I wait until Tor is ready 4:30.821
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:15:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.519 
SCENARIO FAILED: 'Using normal bridges' (at time 00:55:20)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/00:55:20_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:41.979
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 11.270
Then I wait until Tor is ready 4:30.708
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:22:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.533 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 01:00:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:00:22_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.059
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:2.921
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 32.234
Then I wait until Tor is ready 4:30.687
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:29:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.773 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 01:05:43)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:05:43_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.732
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.304
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.300
Then the Tor Connection Assistant reports that it failed to connect 0.114
And tca.conf is empty 0.460
Given I scan a QR code from the error page in Tor Connection Assistant 21.803
And I retry connecting to Tor 1.148
Then I wait until Tor is ready 4:30.599
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:41:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.410 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 01:11:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:11:30_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.060
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:43.612
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 12.802
Then I wait until Tor is ready 4:30.810
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:49:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
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:330 5.444 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:16:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:16:33_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.051
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:53.668
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.606
When I configure a direct connection in the Tor Connection Assistant 20.511
Then I wait until Tor is ready 4:30.550
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:59:in `Then I wait until Tor is ready'
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
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:330 5.530 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:21:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:21:45_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:58.215
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.086
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 22.903
Then the Tor Connection Assistant reports that it failed to connect 0.109
Given the Tor network and default bridges are unblocked 1.713
When I click "Connect to Tor" 1.159
Then I wait until Tor is ready 4:30.241
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:108:in `Then I wait until Tor is ready'
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:330 5.751 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:31:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/01:31:57_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.031
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
4:50.345
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.891
When I log in to a new session in Chinese (zh_CN) 56.924
Then the keyboard layout is set to "cn" 0.263
When the network is plugged 0.074
And Tor is ready 37.090
Then I successfully start the Unsafe Browser 26.647
And I kill the Unsafe Browser 9.161
When I enable the screen keyboard 1.568
Then the screen keyboard works in Tor Browser 1:2.703
And DuckDuckGo is the default search engine 39.806
And I kill the Tor Browser 6.945
And the screen keyboard works in Thunderbird 30.266
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Thunderbird" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1058:in `new'
./features/step_definitions/common_steps.rb:1058:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66: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/common_steps.rb:1057:in `launch_app'
./features/step_definitions/common_steps.rb:1104:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `block in <top (required)>'
./features/step_definitions/thunderbird.rb:212: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/common_steps.rb:1057:in `launch_app'
./features/step_definitions/common_steps.rb:1104:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `/^I start Thunderbird$/'
./features/step_definitions/thunderbird.rb:212:in `/^the screen keyboard works in Thunderbird$/'
features/localization.feature:45:in `And the screen keyboard works in Thunderbird'
features/localization.feature:33:in `And the screen keyboard works in Thunderbird'
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.955 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:48:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:48:13_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:48:13_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:48:13_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:48:13_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:55.743
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 23.702
When I log in to a new session in English (en) 38.482
Then the keyboard layout is set to "us" 0.149
When the network is plugged 0.077
And Tor is ready 34.461
Then I successfully start the Unsafe Browser 38.182
And I kill the Unsafe Browser 6.517
When I enable the screen keyboard 0.142
Then the screen keyboard works in Tor Browser 34.028
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:46:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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
After features/support/hooks.rb:330 6.187 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 03:51:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:51:15_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:51:15_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:51:15_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:51:15_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:13.591
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.718
When I log in to a new session in German (de) 1:0.144
Then the keyboard layout is set to "de" 0.230
When the network is plugged 0.109
And Tor is ready 35.346
Then I successfully start the Unsafe Browser 37.708
And I kill the Unsafe Browser 6.920
When I enable the screen keyboard 0.156
Then the screen keyboard works in Tor Browser 34.255
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:48:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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 "de" 0.000
After features/support/hooks.rb:330 14.297 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 03:59:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/03:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:5.772
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.147
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.217
When I log in to a new session in Italian (it) 59.199
Then the keyboard layout is set to "it" 0.197
When the network is plugged 0.085
And Tor is ready 34.939
Then I successfully start the Unsafe Browser 36.739
And I kill the Unsafe Browser 7.053
When I enable the screen keyboard 0.152
Then the screen keyboard works in Tor Browser 35.188
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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
After features/support/hooks.rb:330 6.457 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:02:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:02:56_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:02:56_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:02:56_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:02:56_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:7.979
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 13.650
When I log in to a new session in Portuguese (pt) 58.993
Then the keyboard layout is set to "pt" 0.412
When the network is plugged 0.122
And Tor is ready 34.170
Then I successfully start the Unsafe Browser 38.966
And I kill the Unsafe Browser 6.850
When I enable the screen keyboard 0.136
Then the screen keyboard works in Tor Browser 34.676
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:54:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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
After features/support/hooks.rb:330 5.917 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:11:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:11:16_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:11:16_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:11:16_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:11:16_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:12.885
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 20.782
When I log in to a new session in Turkish (tr) 58.889
Then the keyboard layout is set to "tr" 0.302
When the network is plugged 0.299
And Tor is ready 32.501
Then I successfully start the Unsafe Browser 39.688
And I kill the Unsafe Browser 6.732
When I enable the screen keyboard 0.135
Then the screen keyboard works in Tor Browser 33.554
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:57:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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
After features/support/hooks.rb:330 11.407 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 04:24:35)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:24:35_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:24:35_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:24:35_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:23.842
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.573
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:23.842
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:13:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
When I log in to a new session without activating the Persistent Storage 0.000
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
After features/support/hooks.rb:330 6.116 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:48:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:48:30_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_feature-arti/96/artifact/build-artifacts/04:48:30_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:48:30_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:48:30_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:27.317
Scenario Creating a Persistent Storage when system is low on memory
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.115
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:27.317
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:31:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And the system is very low on memory 0.000
When I create a file in the Persistent directory 0.000
When I try to create a persistent partition 0.000
Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.000
When I close the Persistent Storage app 0.000
And I free up some memory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
After features/support/hooks.rb:330 6.136 
SCENARIO FAILED: 'Creating a Persistent Storage when system is low on memory' (at time 04:56:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:56:34_Creating_a_Persistent_Storage_when_system_is_low_on_memory.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:56:34_Creating_a_Persistent_Storage_when_system_is_low_on_memory.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:56:34_Creating_a_Persistent_Storage_when_system_is_low_on_memory.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/04:56:34_Creating_a_Persistent_Storage_when_system_is_low_on_memory.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:25.012
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:25.012
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:330 7.408 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 05:04:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:04:30_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:04:30_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:04:30_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:04:30_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:8.789
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 48.535
And the network is plugged 2.855
And Tor is ready 17.397
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:664:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:618:in `/^Tor is ready$/'
features/persistence.feature:75:in `And Tor is ready'
And I take note of which tps features are available 0.000
When I write some files expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 8.721 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 05:05:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:05:49_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:05:49_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:05:49_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:05:49_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
30.090
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 22.810
And I log in to a new session without activating the Persistent Storage 7.279
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:530: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:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 7.540 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 05:31:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:31:10_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:31:10_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:31:10_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:31:10_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:16.087
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.105
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 15.478
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.087
When I try to enable persistence 0.517
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.004
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:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 16.333 
SCENARIO FAILED: 'Feature activation fails' (at time 05:38:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:38:11_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:38:11_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:38:11_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:38:11_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:2.017
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 42.301
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.941
When I try to enable persistence 1.737
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.038
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:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 18.572 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 05:53:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:53:30_Manual_filesystem_repair_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:53:30_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:53:30_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:53:30_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:22.107
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.626
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.109
When I try to enable persistence 0.369
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1: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/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 23.012 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:55:10)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:55:10_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:55:10_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:55:10_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:36.785
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 16.446
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.973
And Tails detects disk read failures on the boot device 1.844
When I try to enable persistence 0.519
Then the Welcome Screen tells me that my hardware is probably failing 1: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/usb.rb:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 23.488 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 05:57:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:57:12_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:57:12_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:57:12_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
2:21.073
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 58.699
And I create a persistent partition with the default settings 51.822
Then the "TorConfiguration" tps feature is not enabled 3.492
When the network is plugged 0.080
And the Tor Connection Assistant autostarts 17.160
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.818
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
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
After features/support/hooks.rb:330 10.653 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:59:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:59:50_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:59:50_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/05:59:50_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
7:7.708
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 47.144
And I create a persistent partition with the default settings 52.527
Then the "TorConfiguration" tps feature is not enabled 3.963
When the network is plugged 0.306
And the Tor Connection Assistant autostarts 16.357
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 36.116
And I wait until Tor is ready 4:31.292
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
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 Disabling persistence of 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 disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 8.760 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 06:07:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:07:07_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:18.059
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.047
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.059
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 8.971 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:18:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:18:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:18:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:18:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:18:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
3:15.021
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails from DVD and logged in and the network is connected 56.057
And a web server is running on the LAN 1.083
And I capture all network traffic 0.015
When I start the Tor Browser 43.350
And the Tor Browser loads the startup page 1.259
And I open a page on the LAN web server in the Tor Browser 33.246
Then the Tor Browser shows the "Unable to connect" error 1:0.008
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./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/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66: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/browser.rb:334: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/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 10.985 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 06:53:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:53:13_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:53:13_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/06:53:13_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.055
Feature: Browsing the web using the Tor Browser
Tags: @product
1:57.018
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.111
Steps
Given I have started Tails from DVD and logged in and the network is connected 24.529
When I start the Tor Browser 44.216
And the Tor Browser loads the startup page 1.350
Then Tor Browser's circuit view is working 46.922
The 
The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Tor Circuit" roleName='push 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/browser.rb:435:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:94:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 10.664 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 07:13:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:13:31_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_feature-arti/96/artifact/build-artifacts/07:13:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:13:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:13:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:11.988
Scenario WebRTC is disabled in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:11.988
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:97:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
When I open the address "https://net.ipcalf.com/" in the Tor Browser 0.000
Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page 0.000
When I open the address "https://mozilla.github.io/webrtc-landing/pc_test.html" in the Tor Browser 0.000
Then Tor Browser displays a "RTCPeerConnection is missing!" heading on the "Simple RTCPeerConnection Video Test" page 0.000
After features/support/hooks.rb:330 5.842 
SCENARIO FAILED: 'WebRTC is disabled in Tor Browser' (at time 07:14:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:14:50_WebRTC_is_disabled_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:14:50_WebRTC_is_disabled_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:14:50_WebRTC_is_disabled_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:14:50_WebRTC_is_disabled_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:12.290
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.290
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:106:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And I successfully configure Tor 0.000
And available upgrades have been checked 0.000
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:330 7.807 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:16:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:16:10_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:16:10_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:16:10_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:16:10_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:14.236
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 19.089
Then the live user's Videos directory exists 0.144
And there is a GNOME bookmark for the Videos directory 2.743
Then I start the Tor Browser in offline mode 52.258
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:131:in `Then I start the Tor Browser in offline mode'
features/torified_browsing.feature:123:in `Then I start the Tor Browser in offline mode'
And I can save the current page as "index.html" to the Videos GNOME bookmark 0.000
After features/support/hooks.rb:330 8.401 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 07:25:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:25:16_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:25:16_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:25:16_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:25:16_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
8:9.535
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:19.958
And all tps features are active 9.547
And all persistent filesystems have safe access rights 0.434
And all persistence configuration files have safe access rights 0.659
And all persistent directories have safe access rights 3.415
When I start the Tor Browser in offline mode 58.269
And I add a bookmark to eff.org in the Tor Browser 29.256
And I cold reboot the computer 28.292
And the computer reboots Tails 1:47.264
And I enable persistence 35.633
And I log in to a new session 1:3.593
And all notifications have disappeared 19.515
And I start the Tor Browser in offline mode 40.163
Then the Tor Browser has a bookmark to eff.org 13.532
cannot 
cannot find TorBrowserEFFBookmark.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:515:in `/^the Tor Browser has a bookmark to eff.org$/'
features/torified_browsing.feature:147:in `Then the Tor Browser has a bookmark to eff.org'
After features/support/hooks.rb:330 7.704 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:33:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:33:34_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:33:34_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:33:34_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:33:34_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.014
Feature: Various checks for torified software
1:11.494
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:509 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:11.494
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_misc.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
0.000
Scenario curl should work for HTTPS and go through Tor
Steps
When I curl "https://example.com/" to stdout 0.000
Then the curl command is successful 0.000
And the curl standard output contains "Example Domain" 0.000
After features/support/hooks.rb:517 0.063
After features/support/hooks.rb:330 5.635 
SCENARIO FAILED: 'curl should work for HTTPS and go through Tor' (at time 07:36:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:36:51_curl_should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:36:51_curl_should_work_for_HTTPS_and_go_through_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:36:51_curl_should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:36:51_curl_should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:12.073
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:12.073
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:51:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 0.000
And I try to start the Unsafe Browser 0.000
Then I see a warning about another instance already running 0.000
After features/support/hooks.rb:330 5.898 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:52:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:52:33_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:52:33_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:52:33_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/07:52:33_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:3.831
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 48.683
And I unlock and mount this VeraCrypt file container with GNOME Disks 15.148
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
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
After features/support/hooks.rb:330 7.989 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 08:13:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/08:13:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/08:13:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/08:13:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/96/artifact/build-artifacts/08:13:50_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.020