Project Number Date
test_Tails_ISO_feature-arti 68 24 May 2025, 16:47

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
4:58.350
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:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.901
When the network is plugged 0.088
And the Tor Connection Assistant autostarts 4.243
And I configure some normal bridges in the Tor Connection Assistant 13.902
And I wait until Tor is ready 4:31.214
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:18:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.037
After features/support/hooks.rb:330 5.217

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

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

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

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

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

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

After features/support/hooks.rb:100 0.000
Feature: Time syncing
4:58.796
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.003
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.207
When I bump the system time with "+1 day" 0.421
And I capture all network traffic 0.002
And the network is plugged 0.088
And the Tor Connection Assistant autostarts 4.348
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 14.435
And I wait until Tor is ready 4:31.292
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:28:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:517 0.031
After features/support/hooks.rb:330 5.335

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

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

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

After features/support/hooks.rb:100 0.062
Feature: Time syncing
5:26.684
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.003
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.911
When I bump the system time with "+8 hours +15 minutes" 0.323
And all notifications have disappeared 4.298
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.107
And the network is plugged 0.067
And the Tor Connection Assistant autostarts 3.786
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.496
And I click "Connect to Tor" 1.146
And the Tor Connection Assistant fails to connect to Tor 15.954
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.978
Then the system clock is less than 20 minutes incorrect 0.232
When I click "Connect to Tor" 1.177
Then I wait until Tor is ready 4:30.200
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:77:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.074
After features/support/hooks.rb:330 5.162

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/00:32:06_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/68/artifact/build-artifacts/00:32:06_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/68/artifact/build-artifacts/00:32:06_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/68/artifact/build-artifacts/00:32:06_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/68/artifact/build-artifacts/00:32:06_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/68/artifact/build-artifacts/00:32:06_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.060
Feature: Time syncing
5:21.526
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:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.184
When I bump the system time with "+8 hours +15 minutes" 0.181
And all notifications have disappeared 4.208
And I capture all network traffic 0.002
And the network is plugged 0.111
And the Tor Connection Assistant autostarts 3.295
# 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.715
And I click "Connect to Tor" 1.174
Then the Tor Connection Assistant reports that it failed to connect 11.848
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.811
Then the system clock is less than 20 minutes incorrect 0.229
# "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.196
Then I wait until Tor is ready 4:30.219
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:99:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 5.335

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/00:37:33_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/68/artifact/build-artifacts/00:37:33_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/68/artifact/build-artifacts/00:37:33_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/68/artifact/build-artifacts/00:37:33_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/68/artifact/build-artifacts/00:37:33_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/68/artifact/build-artifacts/00:37:33_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.079
Tags: @product
4:42.797
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 12.047
Then I wait until Tor is ready 4:30.750
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.306

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

After features/support/hooks.rb:100 0.051
Tags: @product
5:5.944
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 34.306
Then I wait until Tor is ready 4:31.638
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.345

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

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

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

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

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

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

After features/support/hooks.rb:100 0.032
Tags: @product
5:29.264
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.978
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 32.146
Then the Tor Connection Assistant reports that it failed to connect 0.121
And tca.conf is empty 0.282
Given I scan a QR code from the error page in Tor Connection Assistant 22.662
And I retry connecting to Tor 1.172
Then I wait until Tor is ready 4:30.899
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.794

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

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

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

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

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

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

After features/support/hooks.rb:100 0.037
4:45.326
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 14.412
Then I wait until Tor is ready 4:30.913
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.360

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

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

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

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

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

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

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

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

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

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

After features/support/hooks.rb:100 0.035
Tags: @product
4:58.299
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.940
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 23.236
Then the Tor Connection Assistant reports that it failed to connect 0.130
Given the Tor network and default bridges are unblocked 1.694
When I click "Connect to Tor" 1.165
Then I wait until Tor is ready 4:30.131
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.630

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

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

After features/support/hooks.rb:100 0.044
26:59.785
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:509 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 58.324
And I update APT using apt 36.616
And I install "popularity-contest" using apt 23.060
Then I am proposed to add the "popularity-contest" package to my Additional Software 7.758
When I create a persistent storage and activate the Additional Software feature 18.821
Then Additional Software is correctly configured for package "popularity-contest" 3.044
When I shutdown Tails and wait for the computer to power off 13.271
And I start Tails from USB drive "__internal" with network unplugged 1:2.172
And I enable persistence 20.068
And I log in to a new session 40.383
And the Additional Software installation service has started 2:16.152
Then I am notified that the installation succeeded 20:0.110
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:606:in `new'
./features/step_definitions/common_steps.rb:606:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
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:517 0.047
After features/support/hooks.rb:330 10.834

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:19:08)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/02:19:08_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/68/artifact/build-artifacts/02:19:08_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/68/artifact/build-artifacts/02:19:08_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.010
Tags: @product
1:27.102
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.004
Steps
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.529
When I start Tails from USB drive "old" with network unplugged 55.302
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.823

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

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

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

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

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

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

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/02:40:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/02:40:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.008
Tags: @product
36.315
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.005
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 36.133
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.773

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

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

After features/support/hooks.rb:100 0.007
Tags: @product
1:13.542
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.343
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.102

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

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

After features/support/hooks.rb:100 0.008
5:28.686
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.313
And I create a persistent partition with the default settings 21.691
Then the "TorConfiguration" tps feature is not enabled 2.469
When the network is plugged 0.076
And the Tor Connection Assistant autostarts 10.447
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.102
And I wait until Tor is ready 4:30.586
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.616

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:53:38)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:53:38_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
5:22.943
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.466
And I create a persistent partition with the default settings 20.652
Then the "TorConfiguration" tps feature is not enabled 2.455
When the network is plugged 0.061
And the Tor Connection Assistant autostarts 7.251
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.535
And I wait until Tor is ready 4:30.519
Tor
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.357

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:59:07)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/04:59:07_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
3:15.342
Scenario I can reboot Tails via the system menu
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.748
When I request a reboot using the system menu 1.593
Then Tails eventually restarts 3:0.000
try_for() timeout expired
Last ignored exception was: FindFailed: cannot find TailsGreeter.png on the screen
./features/support/helpers/screen.rb:157:in `find'
./features/step_definitions/common_steps.rb:857: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/common_steps.rb:855:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:855:in `/^Tails eventually (shuts down|restarts)$/'
features/shutdown_applet.feature:13:in `Then Tails eventually restarts'
After features/support/hooks.rb:330 10.547

SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 05:07:42)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:07:42_I_can_reboot_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:07:42_I_can_reboot_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:07:42_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
3:24.478
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.074
And I start the Tor Browser 24.304
And the Tor Browser loads the startup page 3:0.099
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/browser.rb:204:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:498:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/tor_stream_isolation.feature:30:in `And the Tor Browser loads the startup page'
Then I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 5.453

SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 05:23:54)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:23:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:23:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:23:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:23:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:57.844
Scenario The Tor Browser cannot access the LAN
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.194
And a web server is running on the LAN 1.035
And I capture all network traffic 0.006
When I start the Tor Browser 31.492
And the Tor Browser loads the startup page 1.124
And I open a page on the LAN web server in the Tor Browser 10.989
Then the Tor Browser shows the "Unable to connect" error 1:0.001
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:334:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 10.503

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:25:57_The_Tor_Browser_cannot_access_the_LAN.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:25:57_The_Tor_Browser_cannot_access_the_LAN.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:25:57_The_Tor_Browser_cannot_access_the_LAN.journal

After features/support/hooks.rb:100 0.057
3:38.012
Scenario Watching a WebM video
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Before features/support/hooks.rb:509 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.354
When I start the Tor Browser 25.570
And the Tor Browser loads the startup page 3:0.087
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/browser.rb:204:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:498:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:46:in `And the Tor Browser loads the startup page'
Then I can watch a WebM video in Tor Browser 0.000
After features/support/hooks.rb:517 0.050
After features/support/hooks.rb:330 5.858

SCENARIO FAILED: 'Watching a WebM video' (at time 05:34:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:34:01_Watching_a_WebM_video.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:34:01_Watching_a_WebM_video.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:34:01_Watching_a_WebM_video.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:34:01_Watching_a_WebM_video.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:20.556
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.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.852
When I start the Tor Browser 31.592
And the Tor Browser loads the startup page 1.130
Then Tor Browser's circuit view is working 32.980
The
The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Tor Circuit" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:435:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:94:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 7.221

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

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

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:38:41_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/68/artifact/build-artifacts/05:38:41_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:100 0.000