Project Number Date
test_Tails_ISO_feature-arti 89 12 Jun 2025, 17:19

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
4:56.868
Scenario Clock with host's time while using bridges
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 8.440
When the network is plugged 0.107
And the Tor Connection Assistant autostarts 4.278
And I configure some normal bridges in the Tor Connection Assistant 13.195
And I wait until Tor is ready 4:30.846
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.189

SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:50)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:16:50_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/89/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.journal

After features/support/hooks.rb:100 0.000
Feature: Time syncing
4:58.304
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.002
Before features/support/hooks.rb:509 0.001
Steps
Given I have started Tails from DVD without network and logged in 8.196
When I bump the system time with "+1 day" 0.374
And I capture all network traffic 0.004
And the network is plugged 0.096
And the Tor Connection Assistant autostarts 4.430
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 14.373
And I wait until Tor is ready 4:30.828
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.028
After features/support/hooks.rb:330 5.227

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:21:54_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/89/artifact/build-artifacts/00:21:54_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/89/artifact/build-artifacts/00:21:54_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/89/artifact/build-artifacts/00:21:54_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:21:54_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/89/artifact/build-artifacts/00:21:54_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal

After features/support/hooks.rb:100 0.050
Feature: Time syncing
5:25.402
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.003
Steps
Given I have started Tails from DVD without network and logged in 8.077
When I bump the system time with "+8 hours +15 minutes" 0.253
And all notifications have disappeared 3.848
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.132
And the network is plugged 0.091
And the Tor Connection Assistant autostarts 3.353
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.753
And I click "Connect to Tor" 1.181
And the Tor Connection Assistant fails to connect to Tor 16.134
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.867
Then the system clock is less than 20 minutes incorrect 0.316
When I click "Connect to Tor" 1.177
Then I wait until Tor is ready 4:30.209
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.035
After features/support/hooks.rb:330 5.476

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:32:09)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:32:09_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/89/artifact/build-artifacts/00:32:09_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/89/artifact/build-artifacts/00:32:09_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/89/artifact/build-artifacts/00:32:09_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/89/artifact/build-artifacts/00:32:09_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/89/artifact/build-artifacts/00:32:09_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.040
Feature: Time syncing
5:21.781
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.006
Before features/support/hooks.rb:509 0.009
Steps
Given I have started Tails from DVD without network and logged in 8.390
When I bump the system time with "+8 hours +15 minutes" 0.252
And all notifications have disappeared 3.812
And I capture all network traffic 0.003
And the network is plugged 0.077
And the Tor Connection Assistant autostarts 4.356
# 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 4.868
And I click "Connect to Tor" 1.235
Then the Tor Connection Assistant reports that it failed to connect 11.805
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 15.021
Then the system clock is less than 20 minutes incorrect 0.243
# "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.360
When I click "Connect to Tor" 1.149
Then I wait until Tor is ready 4:30.203
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.031
After features/support/hooks.rb:330 5.440

SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:37:37)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:37:37_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/89/artifact/build-artifacts/00:37:37_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/89/artifact/build-artifacts/00:37:37_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/89/artifact/build-artifacts/00:37:37_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/89/artifact/build-artifacts/00:37:37_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/89/artifact/build-artifacts/00:37:37_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.034
Tags: @product
4:43.876
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 13.139
Then I wait until Tor is ready 4:30.737
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.324

SCENARIO FAILED: 'Using normal bridges' (at time 00:43:08)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:43:08_Using_normal_bridges.journal

After features/support/hooks.rb:100 0.042
Tags: @product
4:42.695
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 12.111
Then I wait until Tor is ready 4:30.583
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.386

SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:09)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:48:09_Using_obfs4_pluggable_transports.journal

After features/support/hooks.rb:100 0.050
Tags: @product
5:2.112
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 31.090
Then I wait until Tor is ready 4:31.022
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 6.342

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:53:31_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:53:31_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/89/artifact/build-artifacts/00:53:31_Using_obfs4_pluggable_transports_from_a_QR_code.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:53:31_Using_obfs4_pluggable_transports_from_a_QR_code.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:53:31_Using_obfs4_pluggable_transports_from_a_QR_code.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:53:31_Using_obfs4_pluggable_transports_from_a_QR_code.journal

After features/support/hooks.rb:100 0.058
Tags: @product
5:27.885
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.576
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.209
Then the Tor Connection Assistant reports that it failed to connect 0.117
And tca.conf is empty 0.233
Given I scan a QR code from the error page in Tor Connection Assistant 21.623
And I retry connecting to Tor 1.168
Then I wait until Tor is ready 4:30.957
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 6.006

SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:19)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:59:19_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:59:19_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/89/artifact/build-artifacts/00:59:19_TCA_can_scan_QR_code_after_a_connection_failure.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:59:19_TCA_can_scan_QR_code_after_a_connection_failure.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:59:19_TCA_can_scan_QR_code_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/00:59:19_TCA_can_scan_QR_code_after_a_connection_failure.journal

After features/support/hooks.rb:100 0.068
4:48.064
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 16.923
Then I wait until Tor is ready 4:31.140
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.410

SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:29)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:04:29_Default_Tor_bridges.journal

After features/support/hooks.rb:100 0.044
Tags: @product
4:56.141
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.814
When I configure a direct connection in the Tor Connection Assistant 22.367
Then I wait until Tor is ready 4:30.959
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.445

SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:09:43)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:09:43_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/89/artifact/build-artifacts/01:09:43_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/89/artifact/build-artifacts/01:09:43_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/89/artifact/build-artifacts/01:09:43_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/89/artifact/build-artifacts/01:09:43_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/89/artifact/build-artifacts/01:09:43_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal

After features/support/hooks.rb:100 0.039
Tags: @product
4:57.537
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.991
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 22.419
Then the Tor Connection Assistant reports that it failed to connect 0.124
Given the Tor network and default bridges are unblocked 1.572
When I click "Connect to Tor" 1.190
Then I wait until Tor is ready 4:30.239
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.728

SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:20:27)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/01:20:27_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/89/artifact/build-artifacts/01:20:27_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/89/artifact/build-artifacts/01:20:27_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/89/artifact/build-artifacts/01:20:27_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/89/artifact/build-artifacts/01:20:27_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/89/artifact/build-artifacts/01:20:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal

After features/support/hooks.rb:100 0.060
22:5.013
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.006
Steps
Given a computer 0.287
And I start Tails from USB drive "__internal" with network unplugged 1:7.176
And I enable persistence 13.728
And I remove the "cowsay" deb files from the APT cache 0.061
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.094
And I log in to a new session 43.424
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 20:0.240
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:606:in `new'
./features/step_definitions/common_steps.rb:606:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:517 0.062
After features/support/hooks.rb:330 11.344

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:47:23)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:47:23_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:47:23_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:47:23_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.025
Tags: @product
2:10.920
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.386
And I create a 7200 MiB disk named "old" 0.102
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 53.714
When I start Tails from USB drive "old" with network unplugged 1:15.641
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 5.014

SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:49:46)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:49:46_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:49:46_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:49:46_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:49:46_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal

After features/support/hooks.rb:100 0.011
Tags: @product
46.885
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login 46.596
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 4.998

SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:50:38)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:50:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:50:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:50:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:50:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.020
Tags: @product
45.395
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 45.195
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 4.895

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:51:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:51:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:51:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:51:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:51:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.010
Tags: @product
1:26.862
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.440
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:26.422
The
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:302:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.173

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:55:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:55:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:55:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:55:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/02:55:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.009
5:40.780
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 13.487
And I create a persistent partition with the default settings 29.346
Then the "TorConfiguration" tps feature is not enabled 3.725
When the network is plugged 0.071
And the Tor Connection Assistant autostarts 10.252
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 13.232
And I wait until Tor is ready 4:30.664
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
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 6.008

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:25:33)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:25:33_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
5:28.790
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.035
And I create a persistent partition with the default settings 24.681
Then the "TorConfiguration" tps feature is not enabled 2.701
When the network is plugged 0.079
And the Tor Connection Assistant autostarts 8.216
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.279
And I wait until Tor is ready 4:30.796
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
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 5.824

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:31:08)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:31:08_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:56.133
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.415
And a web server is running on the LAN 1.062
And I capture all network traffic 0.010
When I start the Tor Browser 28.462
And the Tor Browser loads the startup page 1.194
And I open a page on the LAN web server in the Tor Browser 12.988
Then the Tor Browser shows the "Unable to connect" error 1:0.000
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 8.481

SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:53:53)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:53:53_The_Tor_Browser_cannot_access_the_LAN.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:53:53_The_Tor_Browser_cannot_access_the_LAN.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/05:53:53_The_Tor_Browser_cannot_access_the_LAN.journal

After features/support/hooks.rb:100 0.033
Tags: @product
1:15.908
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.018
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.831
When I start the Tor Browser 28.712
And the Tor Browser loads the startup page 1.160
Then Tor Browser's circuit view is working 32.203
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 5.659

SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 06:04:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/06:04:05_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/89/artifact/build-artifacts/06:04:05_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/06:04:05_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/89/artifact/build-artifacts/06:04:05_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:100 0.000