Project Number Date
test_Tails_ISO_feature-arti 62 18 May 2025, 16:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
4:57.262
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:509 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.561
When the network is plugged 0.353
And the Tor Connection Assistant autostarts 4.371
And I configure some normal bridges in the Tor Connection Assistant 12.756
And I wait until Tor is ready 4:31.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: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.030
After features/support/hooks.rb:330 5.195 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:16:19_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:16:19_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/62/artifact/build-artifacts/00:16:19_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:16:19_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:16:19_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:16:19_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.330
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 9.349
When I bump the system time with "+1 day" 0.358
And I capture all network traffic 0.003
And the network is plugged 0.080
And the Tor Connection Assistant autostarts 3.628
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 14.076
And I wait until Tor is ready 4:30.835
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.040
After features/support/hooks.rb:330 5.149 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:21:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:21:23_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/62/artifact/build-artifacts/00:21:23_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/62/artifact/build-artifacts/00:21:23_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/62/artifact/build-artifacts/00:21:23_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:21:23_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/62/artifact/build-artifacts/00:21:23_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.053
Feature: Time syncing
Tags: @product @check_tor_leaks
5:25.988
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.309
When I bump the system time with "+8 hours +15 minutes" 0.265
And all notifications have disappeared 3.985
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.112
And the network is plugged 0.062
And the Tor Connection Assistant autostarts 3.584
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 6.234
And I click "Connect to Tor" 1.174
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.806
Then the system clock is less than 20 minutes incorrect 0.262
When I click "Connect to Tor" 1.136
Then I wait until Tor is ready 4:30.096
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.034
After features/support/hooks.rb:330 5.115 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:31:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:31:52_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/62/artifact/build-artifacts/00:31:52_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/62/artifact/build-artifacts/00:31:52_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/62/artifact/build-artifacts/00:31:52_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/62/artifact/build-artifacts/00:31:52_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/62/artifact/build-artifacts/00:31:52_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.043
Feature: Time syncing
Tags: @product @check_tor_leaks
5:20.789
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.001
Steps
Given I have started Tails from DVD without network and logged in 8.189
When I bump the system time with "+8 hours +15 minutes" 0.235
And all notifications have disappeared 4.093
And I capture all network traffic 0.003
And the network is plugged 0.075
And the Tor Connection Assistant autostarts 3.703
# 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.381
And I click "Connect to Tor" 1.207
Then the Tor Connection Assistant reports that it failed to connect 11.905
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.948
Then the system clock is less than 20 minutes incorrect 0.300
# "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.355
When I click "Connect to Tor" 1.197
Then I wait until Tor is ready 4:30.191
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.034
After features/support/hooks.rb:330 5.353 
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:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:37:18_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/62/artifact/build-artifacts/00:37:18_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/62/artifact/build-artifacts/00:37:18_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/62/artifact/build-artifacts/00:37:18_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/62/artifact/build-artifacts/00:37:18_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/62/artifact/build-artifacts/00:37:18_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:45.039
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 14.265
Then I wait until Tor is ready 4:30.773
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.274 
SCENARIO FAILED: 'Using normal bridges' (at time 00:42:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:42:59_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.089
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:42.612
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 11.540
Then I wait until Tor is ready 4:31.072
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.279 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:12)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:48:12_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.044
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:5.110
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.117
Then I wait until Tor is ready 4:30.993
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.441 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:53:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:53:34_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:53:34_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/62/artifact/build-artifacts/00:53:34_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:53:34_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:53:34_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:53:34_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.069
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.691
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.853
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.169
Then the Tor Connection Assistant reports that it failed to connect 0.132
And tca.conf is empty 0.243
Given I scan a QR code from the error page in Tor Connection Assistant 22.176
And I retry connecting to Tor 1.164
Then I wait until Tor is ready 4:30.952
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.309 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:20)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:59:20_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:59:20_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/62/artifact/build-artifacts/00:59:20_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:59:20_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:59:20_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/00:59:20_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:44.071
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 12.933
Then I wait until Tor is ready 4:31.137
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.466 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:04:22_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.148
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.045
When I configure a direct connection in the Tor Connection Assistant 20.971
Then I wait until Tor is ready 4:31.130
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.252 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:09:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:09:34_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/62/artifact/build-artifacts/01:09:34_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/62/artifact/build-artifacts/01:09:34_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/62/artifact/build-artifacts/01:09:34_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/62/artifact/build-artifacts/01:09:34_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/62/artifact/build-artifacts/01:09:34_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.060
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:58.443
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.151
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 23.305
Then the Tor Connection Assistant reports that it failed to connect 0.115
Given the Tor network and default bridges are unblocked 1.552
When I click "Connect to Tor" 1.159
Then I wait until Tor is ready 4:30.158
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.442 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:19:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/01:19:48_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/62/artifact/build-artifacts/01:19:48_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/62/artifact/build-artifacts/01:19:48_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/62/artifact/build-artifacts/01:19:48_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/62/artifact/build-artifacts/01:19:48_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/62/artifact/build-artifacts/01:19:48_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.047
Feature: Upgrading an old Tails USB installation
Tags: @product
1:27.294
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.185
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.092
When I start Tails from USB drive "old" with network unplugged 55.923
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.823 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:19:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:19:14_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/62/artifact/build-artifacts/02:19:14_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:19:14_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/62/artifact/build-artifacts/02:19:14_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
38.835
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.005
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 38.652
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 4.731 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:19:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:19:58_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/62/artifact/build-artifacts/02:19:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:19:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:19:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
38.447
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.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 38.269
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.755 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:20:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:20:41_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/62/artifact/build-artifacts/02:20:41_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/62/artifact/build-artifacts/02:20:41_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/62/artifact/build-artifacts/02:20:41_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
1:12.986
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.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.811
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.011 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:24:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/02:24:37_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/62/artifact/build-artifacts/02:24:37_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/62/artifact/build-artifacts/02:24:37_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/62/artifact/build-artifacts/02:24:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.029
Feature: Packages are up-to-date
Tags: @source
6.176
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:534 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 6.176
Command 
Command failed (pid 52757 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/tmp/tails-amd64-feature_arti@05e65bbcb0+stable@61bc33f4dd-20250518T1007Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/tmp/tails-amd64-feature_arti@05e65bbcb0+stable@61bc33f4dd-20250518T1007Z.build-manifest
INFO: Need to upgrade our own forked package:
  - network-manager (1.42.4-1.0tails1) to Debian bookworm (1.42.4-1+deb12u1)
INFO: Need to upgrade to a new APT snapshot:
  - abseil (20220623.1-1) to Debian bookworm (20220623.1-1+deb12u2)
  - base-files (12.4+deb12u10) to Debian bookworm (12.4+deb12u11)
  - bash (5.2.15-2+b7) to Debian bookworm (5.2.15-2)
  - busybox (1:1.35.0-4+b3) to Debian bookworm (1:1.35.0-4)
  - debian-archive-keyring (2023.3+deb12u1) to Debian bookworm (2023.3+deb12u2)
  - distro-info-data (0.58+deb12u3) to Debian bookworm (0.58+deb12u4)
  - flatpak[flatpak] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[gir1.2-flatpak-1.0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[libflatpak0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - gcc-12[cpp-12] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[g++-12, gcc-12-base, gcc-12] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libatomic1, libasan8] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libcc1-0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libgcc-12-dev, libgfortran5, libgcc-s1] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libitm1, libgomp1, liblsan0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libobjc4] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libquadmath0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libstdc++6, libstdc++-12-dev, libubsan1, libtsan2] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - glib2.0 (2.74.6-2+deb12u5) to Debian bookworm (2.74.6-2+deb12u6)
  - imagemagick[imagemagick-6-common] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - imagemagick[libmagick++-6.q16-8, libmagickcore-6.q16-6, libmagickwand-6.q16-6] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - initramfs-tools (0.142+deb12u1) to Debian bookworm (0.142+deb12u3)
  - libcap2 (1:2.66-4) to Debian bookworm (1:2.66-4+deb12u1)
  - openssl[libssl3] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - openssl[openssl] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - poppler[gir1.2-poppler-0.18] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[libpoppler126, libpoppler-glib8, libpoppler-cpp0v5] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[poppler-utils] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - python3.11[libpython3.11-minimal, libpython3.11-stdlib, libpython3.11] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - python3.11[python3.11, python3.11-minimal] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - qtbase-opensource-src (5.15.8+dfsg-11+deb12u2) to Debian bookworm (5.15.8+dfsg-11+deb12u3)
  - shadow[login] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - shadow[passwd] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - tzdata (2025a-0+deb12u1) to Debian bookworm (2025b-0+deb12u1)
  - wireless-regdb (2022.06.06-1) to Debian bookworm (2025.02.20-1~deb12u1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:325:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:325:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:541 0.000
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:30.178
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.931
And I create a persistent partition with the default settings 23.548
Then the "TorConfiguration" tps feature is not enabled 3.306
When the network is plugged 0.080
And the Tor Connection Assistant autostarts 9.815
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.969
And I wait until Tor is ready 4:30.526
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb: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.650 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:34:20)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:34:20_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:24.398
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.567
And I create a persistent partition with the default settings 21.917
Then the "TorConfiguration" tps feature is not enabled 2.664
When the network is plugged 0.085
And the Tor Connection Assistant autostarts 7.965
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.610
And I wait until Tor is ready 4:30.587
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.400 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:39:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/04:39:50_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:54.222
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.268
And a web server is running on the LAN 1.029
And I capture all network traffic 0.004
When I start the Tor Browser 28.850
And the Tor Browser loads the startup page 1.143
And I open a page on the LAN web server in the Tor Browser 10.923
Then the Tor Browser shows the "Unable to connect" error 1:0.001
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:334:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 9.792 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:00:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:00:54_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:00:54_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:00:54_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.043
Feature: Browsing the web using the Tor Browser
Tags: @product
1:13.042
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 11.299
When I start the Tor Browser 29.396
And the Tor Browser loads the startup page 1.332
Then Tor Browser's circuit view is working 31.014
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:92:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 7.064 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:10:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:10:44_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/62/artifact/build-artifacts/05:10:44_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:10:44_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/62/artifact/build-artifacts/05:10:44_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000