Project Number Date
test_Tails_ISO_feature-arti 28 13 Dec 2024, 16:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
4:56.210
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:269 0.002
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 7.987
When the network is plugged 0.093
And the Tor Connection Assistant autostarts 3.941
And I configure some normal bridges in the Tor Connection Assistant 13.662
And I wait until Tor is ready 4:30.526
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.040
After features/support/hooks.rb:326 5.159

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

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

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

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

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

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

After features/support/hooks.rb:100 0.000
Feature: Time syncing
5:0.167
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:269 0.002
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.040
When I bump the system time with "+1 day" 0.442
And I capture all network traffic 0.002
And the network is plugged 0.109
And the Tor Connection Assistant autostarts 5.128
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.868
And I wait until Tor is ready 4:30.575
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.039
After features/support/hooks.rb:326 5.161

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

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

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

After features/support/hooks.rb:100 0.052
Feature: Time syncing
5:26.083
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:269 0.003
Before features/support/hooks.rb:503 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.286
When I bump the system time with "+8 hours +15 minutes" 0.264
And all notifications have disappeared 3.958
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.142
And the network is plugged 0.089
And the Tor Connection Assistant autostarts 4.379
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.210
And I click "Connect to Tor" 1.162
And the Tor Connection Assistant fails to connect to Tor 15.894
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 15.108
Then the system clock is less than 20 minutes incorrect 0.234
When I click "Connect to Tor" 1.164
Then I wait until Tor is ready 4:30.182
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.043
After features/support/hooks.rb:326 5.460

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:31:40)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:31:40_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/28/artifact/build-artifacts/00:31:40_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/28/artifact/build-artifacts/00:31:40_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/28/artifact/build-artifacts/00:31:40_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/28/artifact/build-artifacts/00:31:40_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/28/artifact/build-artifacts/00:31:40_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.057
Feature: Time syncing
5:21.181
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:269 0.007
Before features/support/hooks.rb:503 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.045
When I bump the system time with "+8 hours +15 minutes" 0.268
And all notifications have disappeared 4.133
And I capture all network traffic 0.002
And the network is plugged 0.066
And the Tor Connection Assistant autostarts 3.497
# 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.586
And I click "Connect to Tor" 1.160
Then the Tor Connection Assistant reports that it failed to connect 11.661
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.842
Then the system clock is less than 20 minutes incorrect 0.217
# "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.345
When I click "Connect to Tor" 1.166
Then I wait until Tor is ready 4:30.184
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.035
After features/support/hooks.rb:326 5.194

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:07)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:37:07_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/28/artifact/build-artifacts/00:37:07_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/28/artifact/build-artifacts/00:37:07_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/28/artifact/build-artifacts/00:37:07_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/28/artifact/build-artifacts/00:37:07_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/28/artifact/build-artifacts/00:37:07_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.043
Tags: @product
4:44.148
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 13.276
Then I wait until Tor is ready 4:30.871
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.361

SCENARIO FAILED: 'Using normal bridges' (at time 00:42:37)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:42:37_Using_normal_bridges.journal

After features/support/hooks.rb:100 0.070
Tags: @product
4:43.417
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 12.490
Then I wait until Tor is ready 4:30.926
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.327

SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:47:39)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:47:39_Using_obfs4_pluggable_transports.journal

After features/support/hooks.rb:100 0.042
Tags: @product
5:9.229
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 38.644
Then I wait until Tor is ready 4:30.584
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.259

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

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

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

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

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

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

After features/support/hooks.rb:100 0.054
Tags: @product
5:28.467
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.391
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.939
Then the Tor Connection Assistant reports that it failed to connect 0.128
And tca.conf is empty 0.227
Given I scan a QR code from the error page in Tor Connection Assistant 21.921
And I retry connecting to Tor 1.231
Then I wait until Tor is ready 4:30.626
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.344

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:58:54_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data

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

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:58:54_TCA_can_scan_QR_code_after_a_connection_failure.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:58:54_TCA_can_scan_QR_code_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/00:58:54_TCA_can_scan_QR_code_after_a_connection_failure.journal

After features/support/hooks.rb:100 0.079
4:44.917
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 13.740
Then I wait until Tor is ready 4:31.176
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.898

SCENARIO FAILED: 'Default Tor bridges' (at time 01:03:58)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/01:03:58_Default_Tor_bridges.journal

After features/support/hooks.rb:100 0.038
Tags: @product
4:53.413
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.027
When I configure a direct connection in the Tor Connection Assistant 20.912
Then I wait until Tor is ready 4:30.473
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.322

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

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

After features/support/hooks.rb:100 0.062
Tags: @product
4:58.671
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.203
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 23.376
Then the Tor Connection Assistant reports that it failed to connect 0.149
Given the Tor network and default bridges are unblocked 1.550
When I click "Connect to Tor" 1.187
Then I wait until Tor is ready 4:30.204
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.268

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

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

After features/support/hooks.rb:100 0.031
Tags: @product
2:29.791
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.370
When I start Tails from USB drive "old" with network unplugged 1:57.099
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:724:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:724:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.869

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:30:42_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/28/artifact/build-artifacts/02:30:42_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:30:42_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/28/artifact/build-artifacts/02:30:42_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal

After features/support/hooks.rb:100 0.025
Tags: @product
1:6.683
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:6.458
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:724:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:724:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.879

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

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

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:31:53_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:31:53_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.011
Tags: @product
1:4.364
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.168
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:724:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:724:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.987

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:33:03_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/28/artifact/build-artifacts/02:33:03_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/28/artifact/build-artifacts/02:33:03_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/28/artifact/build-artifacts/02:33:03_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.012
Tags: @product
1:27.965
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:27.748
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:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700: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:326 5.066

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/02:37:11_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/28/artifact/build-artifacts/02:37:11_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/28/artifact/build-artifacts/02:37:11_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/28/artifact/build-artifacts/02:37:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.011
Tags: @product
1:46.711
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 1.837
And I start the computer from DVD with network unplugged 43.922
When Tails detects disk read failures on the boot device with a target error 0.948
Then I see a disk failure message on the splash screen 1:0.002
cannot find PlymouthDiskFailureMessage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/hardware.rb:62:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:16:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'
After features/support/hooks.rb:326 4.914

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#3)' (at time 03:06:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:06:28_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:06:28_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:06:28_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:06:28_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.journal

After features/support/hooks.rb:100 0.009
1:34.384
Scenario MAT can clean a PNG file
Before features/support/hooks.rb:269 0.008
Steps
Given a computer 0.258
And I start Tails from DVD with network unplugged and I login 1:34.125
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:723:in `new'
./features/step_definitions/common_steps.rb:723:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:283:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/mat.feature:9:in `And I start Tails from DVD with network unplugged and I login'
And I plug and mount a USB drive containing a sample PNG 0.000
Then MAT can clean some sample PNG file 0.000
After features/support/hooks.rb:326 5.049

SCENARIO FAILED: 'MAT can clean a PNG file' (at time 03:51:23)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:51:23_MAT_can_clean_a_PNG_file.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:51:23_MAT_can_clean_a_PNG_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:51:23_MAT_can_clean_a_PNG_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/03:51:23_MAT_can_clean_a_PNG_file.journal

After features/support/hooks.rb:100 0.008
5:34.549
Background
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.249
And I create a persistent partition with the default settings 27.172
Then the "TorConfiguration" tps feature is not enabled 1.507
When the network is plugged 0.076
And the Tor Connection Assistant autostarts 12.144
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.741
And I wait until Tor is ready 4:30.656
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.688

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:46:06)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:46:06_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
5:28.971
Background
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.692
And I create a persistent partition with the default settings 25.620
Then the "TorConfiguration" tps feature is not enabled 1.242
When the network is plugged 0.110
And the Tor Connection Assistant autostarts 7.048
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 13.757
And I wait until Tor is ready 4:30.499
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.432

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:51:41)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/04:51:41_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:53.113
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.596
And a web server is running on the LAN 1.036
And I capture all network traffic 0.008
When I start the Tor Browser 27.326
And the Tor Browser loads the startup page 1.080
And I open a page on the LAN web server in the Tor Browser 11.049
Then the Tor Browser shows the "Unable to connect" error 1:0.015
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:317:in `headings_in_page'
./features/step_definitions/browser.rb:321:in `page_has_heading'
./features/step_definitions/browser.rb:332: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:331: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:331: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:326 5.499

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:14:02_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:14:02_The_Tor_Browser_cannot_access_the_LAN.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:14:02_The_Tor_Browser_cannot_access_the_LAN.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:14:02_The_Tor_Browser_cannot_access_the_LAN.journal

After features/support/hooks.rb:100 0.043
Tags: @product
1:11.238
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.355
When I start the Tor Browser 28.872
And the Tor Browser loads the startup page 1.020
Then Tor Browser's circuit view is working 27.990
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:432:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:107:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:326 9.143

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:23:37_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:23:37_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/28/artifact/build-artifacts/05:23:37_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:100 0.000