Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 10 25 Jun 2025, 21:51

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
1:8.505
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 14.215
When the network is plugged 54.290
Command 
Command failed (pid 8549 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.046
After features/support/hooks.rb:330 6.134 
SCENARIO FAILED: 'Clock with host's time' (at time 00:13:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
34.263
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.002
Steps
Given I have started Tails from DVD without network and logged in 12.166
When the network is plugged 22.097
Command 
Command failed (pid 8702 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.040
After features/support/hooks.rb:330 6.534 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:14:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_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
35.851
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.003
Steps
Given I have started Tails from DVD without network and logged in 13.309
When I bump the system time with "+1 day" 0.387
And I capture all network traffic 0.007
And the network is plugged 22.147
Command 
Command failed (pid 8857 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:25:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 0.000
And I wait until Tor is ready 0.000
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.038
After features/support/hooks.rb:330 6.106 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:15:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.055
Feature: Time syncing
Tags: @product @check_tor_leaks
2:37.482
Scenario On a clock with host's time, Tor Connection works even if time sync fails
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 9.807
And I make sure time sync before Tor connects times out 1.775
When the network is plugged 2:25.898
Command 
Command failed (pid 9714 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:58:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.046
After features/support/hooks.rb:330 6.010 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:22:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.001
Feature: Time syncing
Tags: @product @check_tor_leaks
1:35.360
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.002
Steps
Given I have started Tails from DVD without network and logged in 10.877
When I bump the system time with "+8 hours +15 minutes" 0.377
And all notifications have disappeared 5.173
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.202
And the network is plugged 1:18.727
Command 
Command failed (pid 9867 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:68:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 0.000
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 6.301 
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:24:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24:35_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.051
Feature: Time syncing
Tags: @product @check_tor_leaks
48.714
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.036
Before features/support/hooks.rb:509 0.024
Steps
Given I have started Tails from DVD without network and logged in 10.453
When I bump the system time with "+8 hours +15 minutes" 0.222
And all notifications have disappeared 5.277
And I capture all network traffic 0.005
And the network is plugged 32.756
Command 
Command failed (pid 10026 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:87:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
# 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 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
# "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.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
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.038
After features/support/hooks.rb:330 6.376 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:25:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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.063
Feature: Time syncing
Tags: @product @check_tor_leaks
1:39.618
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
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.977
And I make sure time sync before Tor connects uses a fake connectivity check service 2.148
And the network is plugged 1:27.492
Command 
Command failed (pid 10181 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:108:in `And the network is plugged'
And Tor is ready 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
When I make NetworkManager perform a connectivity check 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
And the HTTP requests received by the fake connectivity check service are identical 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 6.370 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:27:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.001
Feature: Using Tor bridges and pluggable transports
1:32.865
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 16.338
And I capture all network traffic 0.008
When the network is plugged 1:16.518
Command 
Command failed (pid 10339 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.120 
SCENARIO FAILED: 'Using normal bridges' (at time 00:28:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:28:56_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
48.303
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 14.247
And I capture all network traffic 0.027
When the network is plugged 34.028
Command 
Command failed (pid 10491 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 6.477 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:29:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:29:50_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
19.065
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.792
And I capture all network traffic 0.003
When the network is plugged 10.269
Command 
Command failed (pid 10643 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
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 0.000
Then I wait until Tor is ready 0.000
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.837 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:30:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.035
Feature: Using Tor bridges and pluggable transports
33.489
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 23.217
And I capture all network traffic 0.002
When the network is plugged 10.269
Command 
Command failed (pid 10905 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given I scan a QR code from the error page in Tor Connection Assistant 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
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.951 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:30:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:30:55_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
53.458
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 42.571
And I capture all network traffic 0.003
When the network is plugged 10.883
Command 
Command failed (pid 11280 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
0.000
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
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.792 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:31:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:31:55_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
35.110
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 12.958
And I capture all network traffic 0.048
When the network is plugged 22.103
Command 
Command failed (pid 11429 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 0.000
When 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 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 6.089 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:32:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:32:36_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
53.907
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 43.561
And I capture all network traffic 0.003
When the network is plugged 10.342
Command 
Command failed (pid 11855 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given the Tor network and default bridges are unblocked 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.928 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:33:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:33:36_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.033
Feature: Using Tor bridges and pluggable transports
54.710
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 43.530
And I capture all network traffic 0.004
When the network is plugged 11.175
Command 
Command failed (pid 12221 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Normal bridges are not allowed in "Hide" mode
Steps
When I try to configure some normal bridges in the Tor Connection Assistant in hide mode 0.000
Then the Tor Connection Assistant complains that normal bridges are not allowed 0.000
And I cannot click the "Connect to Tor" button 0.000
After features/support/hooks.rb:330 6.199 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:34:37)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:34:37_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:100 0.060
Feature: Using Tor bridges and pluggable transports
1:0.472
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 47.988
And I capture all network traffic 0.012
When the network is plugged 12.471
Command 
Command failed (pid 12588 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
When I disconnect the network through GNOME 0.000
And I connect the network through GNOME 0.000
Then the Tor Connection Assistant autostarts 0.000
And the Tor Connection Assistant connects to Tor 0.000
And I wait until Tor is ready 0.000
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 12.133 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:35:44)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1750862498/016relay/diff-cache/1245.tmp
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:35:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.051
Feature: Using Tor bridges and pluggable transports
21.738
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD without network and logged in 10.003
And I capture all network traffic 0.046
When the network is plugged 11.689
Command 
Command failed (pid 12743 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Reconnecting from an unblocked network to a blocked network displays an error
Steps
Given I configure a direct connection in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
And I disconnect the network through GNOME 0.000
And the Tor network and default bridges are blocked 0.000
When I connect the network through GNOME 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
After features/support/hooks.rb:330 6.225 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:36:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:36:18_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.051
Feature: Using Tor bridges and pluggable transports
1:11.234
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD without network and logged in 1:11.234
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/tor_bridges.feature:8:in `Given I have started Tails from DVD without network and logged in'
And I capture all network traffic 0.000
When the network is plugged 0.000
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
Given the Tor network and default bridges are unblocked 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 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.394 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:37:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:37:35_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:37:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:37:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:37:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:57.975
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD without network and logged in 24.810
And I prepare Tails for memory erasure tests 4.736
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 1:8.347
Then I find very few patterns in the guest's memory 4.717 
Pattern coverage: 0.000% (0 MiB out of 873 MiB reference memory)
# write cache
When I fill the USB drive with a known pattern 6.517
Then patterns cover at least 99% of the test FS size in the guest's memory 8.845
93.223% 
93.223% of the test FS size (91.490234375 MiB) has the pattern, but more than 99.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/erase_memory.feature:54:in `Then patterns cover at least 99% of the test FS size in the guest's memory'
Output 1 
Pattern coverage: 93.223% (85 MiB out of 91 MiB reference memory)
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
After features/support/hooks.rb:330 7.073 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:44:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:44:01_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:44:01_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:44:01_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:44:01_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.008
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
13:2.962
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13:2.962
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 6.451 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:58:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:58:32_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:58:32_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:58:32_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:58:32_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.012
Feature: Installing Tails to a USB drive
Tags: @product
11:52.707
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11:52.707
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 5.736 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:21:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:21:18_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:21:18_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:21:18_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:21:18_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.005
Feature: Installing Tails to a USB drive
Tags: @product
10:53.072
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10:53.072
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I temporarily create a 7200 MiB disk named "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.840 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 01:32:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:32:17_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:32:17_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:32:17_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:32:17_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:33.777
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.006
Steps
Given a computer 0.211
And I start Tails from USB drive "__internal" and I login with an administration password 4:33.566
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./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/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update APT using apt 0.000
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 5.870 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:59:52)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/01:59:52_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Using Evince
Tags: @product
1:17.252
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.252
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.000
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000
Then I see "CupsTestPage.png" after at most 40 seconds 0.000
And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000
After features/support/hooks.rb:330 6.528 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 03:13:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/03:13:14_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/03:13:14_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/03:13:14_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/03:13:14_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:8.309
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.905
When I log in to a new session in Portuguese (pt) 40.422
Then the keyboard layout is set to "pt" 0.286
When the network is plugged 0.096
And Tor is ready 12.598
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:54:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 5.385 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:15:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:15:52_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:15:52_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:15:52_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:15:52_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:12.799
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.439
When I log in to a new session in Russian (ru) 52.450
Then the keyboard layout is set to "ru" 0.147
When the network is plugged 0.079
And Tor is ready 11.682
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:55:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ru" 0.000
After features/support/hooks.rb:330 6.369 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:17:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:17:11_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:17:11_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:17:11_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/04:17:11_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:15.973
Scenario Feature activation fails
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 with a persistent partition and stopped at Tails Greeter's login screen 1:15.973
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:143:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.000
When I try to enable persistence 0.000
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 5.555 
SCENARIO FAILED: 'Feature activation fails' (at time 05:22:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:22:38_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:22:38_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:22:38_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:22:38_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:17.150
Scenario Automatic filesystem repair
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:17.150
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:166:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And I corrupt the Persistent Storage filesystem on USB drive "__internal" 0.000
When I enable persistence 0.000
Then the filesystem of the Persistent Storage was repaired 0.000
And persistence is successfully enabled 0.000
After features/support/hooks.rb:330 6.200 
SCENARIO FAILED: 'Automatic filesystem repair' (at time 05:34:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:34:59_Automatic_filesystem_repair.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:34:59_Automatic_filesystem_repair.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:34:59_Automatic_filesystem_repair.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:34:59_Automatic_filesystem_repair.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:38.830
Scenario Manual filesystem repair is successful
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 with a persistent partition and stopped at Tails Greeter's login screen 21.951
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.407
When I try to enable persistence 0.454
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.018
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 21.216 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 05:36:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:36:54_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:36:54_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:36:54_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:24.569
Scenario Manual filesystem repair fails
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 with a persistent partition and stopped at Tails Greeter's login screen 21.687
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.952
When I try to enable persistence 1.923
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.005
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 20.080 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:38:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:38:37_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:38:37_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:38:37_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:22.378
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.082
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:22.378
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistent_tor_bridges.feature:8:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And I create a persistent partition with the default settings 0.000
Then the "TorConfiguration" tps feature is not enabled 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
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.819 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:44:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:44:36_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:44:36_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:44:36_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:44:36_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:50.080
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 23.337
And I create a persistent partition with the default settings 57.105
Then the "TorConfiguration" tps feature is not enabled 3.110
When the network is plugged 0.070
And the Tor Connection Assistant autostarts 15.708
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.748
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
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 6.991 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:46:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:46:33_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:46:33_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:46:33_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/05:46:33_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
3:9.860
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 17.512
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.401
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.454
When I accept the autoconfiguration wizard's configuration 2:51.491
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/thunderbird.rb:118:in `wait_for_thunderbird_progress_bar_to_vanish'
./features/step_definitions/thunderbird.rb:159:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:517 0.092
After features/support/hooks.rb:330 12.874 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 06:08:33)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:08:33_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:08:33_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:08:33_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
47.967
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 21.076
Then the Tor Connection Assistant reports that I am not connected to a local network 10.938
When I plug a Wi-Fi adapter 2.211
Then Tor Connection suggests me to connect to Wi-Fi 0.724
And I click on the Wi-Fi settings 1.393
And The Wi-Fi settings are displayed 11.623
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-control-center" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/tor.rb:1113:in `new'
./features/step_definitions/tor.rb:1113:in `/^The Wi-Fi settings are displayed$/'
features/tor_connection.feature:15:in `And The Wi-Fi settings are displayed'
After features/support/hooks.rb:330 6.955 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 06:09:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:09:54_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:09:54_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:09:54_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/06:09:54_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000