Project Number Date
test_Tails_ISO_feature-arti 24 10 Apr 2025, 19:11

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
4:56.965
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.922
When the network is plugged 0.085
And the Tor Connection Assistant autostarts 4.395
And I configure some normal bridges in the Tor Connection Assistant 12.506
And I wait until Tor is ready 4:31.056
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:515 0.040
After features/support/hooks.rb:330 5.165 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:16:57_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:16:57_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/24/artifact/build-artifacts/00:16:57_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:16:57_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:16:57_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:16:57_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
4:58.279
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:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.342
When I bump the system time with "+1 day" 0.357
And I capture all network traffic 0.005
And the network is plugged 0.135
And the Tor Connection Assistant autostarts 4.283
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 14.346
And I wait until Tor is ready 4:30.807
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:515 0.037
After features/support/hooks.rb:330 5.197 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:22:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:22:00_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/24/artifact/build-artifacts/00:22:00_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/24/artifact/build-artifacts/00:22:00_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/24/artifact/build-artifacts/00:22:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:22:00_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/24/artifact/build-artifacts/00:22:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.049
Feature: Time syncing
Tags: @product @check_tor_leaks
5:26.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:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.219
When I bump the system time with "+8 hours +15 minutes" 0.231
And all notifications have disappeared 4.109
And I capture all network traffic 0.004
And I make sure time sync before Tor connects fails 0.131
And the network is plugged 0.078
And the Tor Connection Assistant autostarts 3.781
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.415
And I click "Connect to Tor" 1.183
And the Tor Connection Assistant fails to connect to Tor 16.273
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.973
Then the system clock is less than 20 minutes incorrect 0.657
When I click "Connect to Tor" 1.188
Then I wait until Tor is ready 4:30.153
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:515 0.035
After features/support/hooks.rb:330 5.237 
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:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:32:11_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/24/artifact/build-artifacts/00:32:11_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/24/artifact/build-artifacts/00:32:11_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/24/artifact/build-artifacts/00:32:11_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/24/artifact/build-artifacts/00:32:11_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/24/artifact/build-artifacts/00:32:11_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.049
Feature: Time syncing
Tags: @product @check_tor_leaks
5:20.954
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.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.313
When I bump the system time with "+8 hours +15 minutes" 0.206
And all notifications have disappeared 4.262
And I capture all network traffic 0.003
And the network is plugged 0.132
And the Tor Connection Assistant autostarts 3.670
# 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.482
And I click "Connect to Tor" 1.169
Then the Tor Connection Assistant reports that it failed to connect 11.757
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.915
Then the system clock is less than 20 minutes incorrect 0.231
# "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.419
When I click "Connect to Tor" 1.189
Then I wait until Tor is ready 4:30.198
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:515 0.040
After features/support/hooks.rb:330 5.411 
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/24/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/24/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/24/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/24/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/24/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/24/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.047
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.742
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 12.604
Then I wait until Tor is ready 4:31.138
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.333 
SCENARIO FAILED: 'Using normal bridges' (at time 00:43:06)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:43:06_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:42.663
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 11.581
Then I wait until Tor is ready 4:31.082
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.462 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:48:07_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.047
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:2.981
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.965
Then I wait until Tor is ready 4:31.016
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:29:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.313 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:53:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:53:28_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:53:28_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/24/artifact/build-artifacts/00:53:28_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:53:28_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:53:28_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:53:28_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.839
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.287
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.295
Then the Tor Connection Assistant reports that it failed to connect 0.163
And tca.conf is empty 0.279
Given I scan a QR code from the error page in Tor Connection Assistant 21.536
And I retry connecting to Tor 1.213
Then I wait until Tor is ready 4:31.065
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:41:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.191 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:59:17_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:59:17_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/24/artifact/build-artifacts/00:59:17_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:59:17_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:59:17_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/00:59:17_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.038
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:44.078
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 13.312
Then I wait until Tor is ready 4:30.765
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.295 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:04:19_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.035
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:55.473
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.032
When I configure a direct connection in the Tor Connection Assistant 22.624
Then I wait until Tor is ready 4:30.816
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.227 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:09:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:09:31_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/24/artifact/build-artifacts/01:09:31_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/24/artifact/build-artifacts/01:09:31_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/24/artifact/build-artifacts/01:09:31_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/24/artifact/build-artifacts/01:09:31_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/24/artifact/build-artifacts/01:09:31_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:57.028
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.838
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 21.995
Then the Tor Connection Assistant reports that it failed to connect 0.129
Given the Tor network and default bridges are unblocked 1.647
When I click "Connect to Tor" 1.190
Then I wait until Tor is ready 4:30.226
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.558 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:19:40)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/01:19:40_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/24/artifact/build-artifacts/01:19:40_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/24/artifact/build-artifacts/01:19:40_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/24/artifact/build-artifacts/01:19:40_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/24/artifact/build-artifacts/01:19:40_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/24/artifact/build-artifacts/01:19:40_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.052
Feature: Additional software
Tags: @product @check_tor_leaks @slow
36:16.561
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:16.542
And I update APT using apt 35:0.019
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./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/misc_helpers.rb:180:in `new'
./features/support/helpers/misc_helpers.rb:180:in `force_new_tor_circuit'
./features/support/helpers/misc_helpers.rb:192:in `block in retry_tor'
./features/support/helpers/misc_helpers.rb:222:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:59:in `/^I update APT using apt$/'
features/additional_software_packages.feature:29:in `And I update APT using apt'
And I install "popularity-contest" using apt 0.000
Then I am proposed to add the "popularity-contest" package to my Additional Software 0.000
When I create a persistent storage and activate the Additional Software feature 0.000
Then Additional Software is correctly configured for package "popularity-contest" 0.000
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:330 10.828 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 02:29:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:29:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:29:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:29:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.001
Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:6.126
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.192
And I start Tails from USB drive "__internal" and I login with an administration password 1:53.073
And I update APT using apt 43.002
When I install "makepp" using apt 23.355
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 1:6.501
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/additional_software_packages.rb:157:in `/^the Additional Software dpkg hook has been run for package "([^"]*)" and notices the persistence is locked$/'
features/additional_software_packages.feature:49:in `Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked'
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.029
After features/support/hooks.rb:330 6.328 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:33:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:33:34_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow
1:16.719
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.199
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:16.519
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/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.040
After features/support/hooks.rb:330 5.347 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:34:57)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:34:57_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
1:14.830
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.171
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:14.658
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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
# 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.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.030
After features/support/hooks.rb:330 5.332 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:36:17)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:36:17_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
1:23.108
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.004
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.181
And I start Tails from USB drive "__internal" with network unplugged 1:9.026
And I enable persistence 13.900
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/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
# 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.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
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:515 0.042
After features/support/hooks.rb:330 5.648 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:37:46)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:37:46_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/24/artifact/build-artifacts/02:37:46_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
2:1.709
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.005
Steps
Given a computer 0.283
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 55.650
When I start Tails from USB drive "old" with network unplugged 1:4.624
FileNotFoundError: 
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 4.964 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:39:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:39:53_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/24/artifact/build-artifacts/02:39:53_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:39:53_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/24/artifact/build-artifacts/02:39:53_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
42.733
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.004
Steps
Given a computer 0.302
And I start Tails from USB drive "old" with network unplugged and I login 42.430
FileNotFoundError: 
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 5.807 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:40:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:40:41_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/24/artifact/build-artifacts/02:40:41_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:40:41_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:40:41_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
41.614
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.003
Steps
Given a computer 2.287
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 39.327
FileNotFoundError: 
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.796 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:41:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:41: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/24/artifact/build-artifacts/02:41: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/24/artifact/build-artifacts/02:41: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/24/artifact/build-artifacts/02:41:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:32.001
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 1.842
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:30.158
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.349 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:45:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/02:45:50_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/24/artifact/build-artifacts/02:45:50_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/24/artifact/build-artifacts/02:45:50_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/24/artifact/build-artifacts/02:45:50_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.007
Feature: Tails persistence
Tags: @product
23:0.240
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.681
And the network is plugged 0.661
And Tor is ready 24.040
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.196
And I shutdown Tails and wait for the computer to power off 11.691
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:12.969
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./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:730:in `new'
./features/step_definitions/common_steps.rb:730:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:309: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/persistence.feature:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 11.117 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:53:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/04:53:29_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/04:53:29_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/04:53:29_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.007
Feature: Using persistent Tor bridges and pluggable transports
5:36.149
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 13.490
And I create a persistent partition with the default settings 27.046
Then the "TorConfiguration" tps feature is not enabled 3.029
When the network is plugged 0.077
And the Tor Connection Assistant autostarts 9.990
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.832
And I wait until Tor is ready 4:30.682
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario 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 5.789 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:27:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:27:42_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:27.740
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.626
And I create a persistent partition with the default settings 24.824
Then the "TorConfiguration" tps feature is not enabled 2.586
When the network is plugged 0.087
And the Tor Connection Assistant autostarts 6.883
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.220
And I wait until Tor is ready 4:30.512
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.365 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:33:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:33:16_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:58.394
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 13.143
And a web server is running on the LAN 1.030
And I capture all network traffic 0.006
When I start the Tor Browser 28.102
And the Tor Browser loads the startup page 1.194
And I open a page on the LAN web server in the Tor Browser 14.916
Then the Tor Browser shows the "Unable to connect" error 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:324:in `headings_in_page'
./features/step_definitions/browser.rb:328:in `page_has_heading'
./features/step_definitions/browser.rb:339: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:338: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:338: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.034 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:55:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:55:47_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/24/artifact/build-artifacts/05:55:47_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:55:47_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/05:55:47_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.051
Feature: Browsing the web using the Tor Browser
Tags: @product
1:16.625
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.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.230
When I start the Tor Browser 31.582
And the Tor Browser loads the startup page 1.702
Then Tor Browser's circuit view is working 30.109
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:439:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:93:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 5.558 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 06:05:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/06:05:51_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/24/artifact/build-artifacts/06:05:51_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/06:05:51_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/24/artifact/build-artifacts/06:05:51_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000