Project Number Date
test_Tails_ISO_20267-webtunnel 5 15 Jul 2025, 00:44

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
59.495
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Before features/support/hooks.rb:507 0.022
Steps
Given I have started Tails from DVD without network and logged in 47.945
When the network is plugged 11.550
Command 
Command failed (pid 5881 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.042
After features/support/hooks.rb:330 14.119 
SCENARIO FAILED: 'Clock with host's time' (at time 00:19:44)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:19:44_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
45.918
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.048
Before features/support/hooks.rb:507 0.022
Steps
Given I have started Tails from DVD without network and logged in 31.797
When the network is plugged 14.121
Command 
Command failed (pid 6200 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.043
After features/support/hooks.rb:330 13.268 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:20:45)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1752518036/012relay/diff-cache/1047
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:20:45_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
58.923
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.016
Before features/support/hooks.rb:507 0.014
Steps
Given I have started Tails from DVD without network and logged in 11.254
When I bump the system time with "+1 day" 5.657
And I capture all network traffic 0.457
And the network is plugged 41.553
Command 
Command failed (pid 6359 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.045
After features/support/hooks.rb:330 5.808 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:21:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:21:57_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:21:57_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_20267-webtunnel/5/artifact/build-artifacts/00:21:57_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:21:57_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:21:57_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:21:57_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.059
Feature: Time syncing
Tags: @product @check_tor_leaks
34.943
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:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 20.281
And I make sure time sync before Tor connects times out 1.561
When the network is plugged 13.099
Command 
Command failed (pid 7758 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.039
After features/support/hooks.rb:330 8.420 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:30:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:30:41_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_20267-webtunnel/5/artifact/build-artifacts/00:30:41_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_20267-webtunnel/5/artifact/build-artifacts/00:30:41_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_20267-webtunnel/5/artifact/build-artifacts/00:30:41_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_20267-webtunnel/5/artifact/build-artifacts/00:30:41_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_20267-webtunnel/5/artifact/build-artifacts/00:30:41_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.003
Feature: Time syncing
Tags: @product @check_tor_leaks
46.084
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.068
Before features/support/hooks.rb:507 0.067
Steps
Given I have started Tails from DVD without network and logged in 19.591
When I bump the system time with "+8 hours +15 minutes" 4.739
And all notifications have disappeared 9.447
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.115
And the network is plugged 12.187
Command 
Command failed (pid 7919 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.052
After features/support/hooks.rb:330 6.145 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:31:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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_20267-webtunnel/5/artifact/build-artifacts/00:31:36_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.044
Feature: Time syncing
Tags: @product @check_tor_leaks
1:13.729
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.003
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 48.564
When I bump the system time with "+8 hours +15 minutes" 2.808
And all notifications have disappeared 8.586
And I capture all network traffic 0.003
And the network is plugged 13.767
Command 
Command failed (pid 8306 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.035
After features/support/hooks.rb:330 6.159 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:32:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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_20267-webtunnel/5/artifact/build-artifacts/00:32:57_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.041
Feature: Time syncing
Tags: @product @check_tor_leaks
56.178
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:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 27.999
And I make sure time sync before Tor connects uses a fake connectivity check service 3.571
And the network is plugged 24.607
Command 
Command failed (pid 8572 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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:515 0.045
After features/support/hooks.rb:330 6.610 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:33:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:33:59_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_20267-webtunnel/5/artifact/build-artifacts/00:33:59_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_20267-webtunnel/5/artifact/build-artifacts/00:33:59_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_20267-webtunnel/5/artifact/build-artifacts/00:33:59_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_20267-webtunnel/5/artifact/build-artifacts/00:33:59_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_20267-webtunnel/5/artifact/build-artifacts/00:33:59_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.000
Feature: Using Tor bridges and pluggable transports
1:16.349
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Steps
Given I have started Tails from DVD without network and logged in 1:4.173
And I capture all network traffic 0.096
When the network is plugged 12.079
Command 
Command failed (pid 9047 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 10.802 
SCENARIO FAILED: 'Using normal bridges' (at time 00:35:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:35:23_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
26.956
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.100
Steps
Given I have started Tails from DVD without network and logged in 14.332
And I capture all network traffic 0.116
When the network is plugged 12.508
Command 
Command failed (pid 9201 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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.450 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:36:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:00_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
34.656
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 20.769
And I capture all network traffic 0.086
When the network is plugged 13.801
Command 
Command failed (pid 9365 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 9.062 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:36:42)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1752518036/022obfs4/diff-cache/1018.tmp
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:36:42_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
30.919
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.100
Steps
Given I have started Tails from DVD without network and logged in 18.108
And I capture all network traffic 0.064
When the network is plugged 12.746
Command 
Command failed (pid 9520 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 7.386 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:37:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:22_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:22_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_20267-webtunnel/5/artifact/build-artifacts/00:37:22_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:22_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:22_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:22_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.042
Feature: Using Tor bridges and pluggable transports
28.551
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD without network and logged in 18.082
And I capture all network traffic 0.003
When the network is plugged 10.465
Command 
Command failed (pid 9677 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 6.296 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:37:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:37:58_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.062
Feature: Using Tor bridges and pluggable transports
54.343
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 30.760
And I capture all network traffic 0.180
When the network is plugged 23.402
Command 
Command failed (pid 9933 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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.841 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:38:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:38:59_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_20267-webtunnel/5/artifact/build-artifacts/00:38:59_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_20267-webtunnel/5/artifact/build-artifacts/00:38:59_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_20267-webtunnel/5/artifact/build-artifacts/00:38:59_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_20267-webtunnel/5/artifact/build-artifacts/00:38:59_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_20267-webtunnel/5/artifact/build-artifacts/00:38:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.044
Feature: Using Tor bridges and pluggable transports
1:16.620
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 1:3.898
And I capture all network traffic 0.166
When the network is plugged 12.555
Command 
Command failed (pid 10423 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 12.782 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:40:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:40:23_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.059
Feature: Using Tor bridges and pluggable transports
29.667
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.063
Steps
Given I have started Tails from DVD without network and logged in 14.979
And I capture all network traffic 0.298
When the network is plugged 14.389
Command 
Command failed (pid 10580 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 15.477 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:41:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:41:09_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
41.042
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 28.142
And I capture all network traffic 0.087
When the network is plugged 12.812
Command 
Command failed (pid 10845 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 9.100 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:42:02)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:02_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_20267-webtunnel/5/artifact/build-artifacts/00:42:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
33.461
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.116
Steps
Given I have started Tails from DVD without network and logged in 19.832
And I capture all network traffic 0.134
When the network is plugged 13.494
Command 
Command failed (pid 11002 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 15.785 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:42:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:48_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_20267-webtunnel/5/artifact/build-artifacts/00:42:48_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_20267-webtunnel/5/artifact/build-artifacts/00:42:48_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:48_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:48_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:42:48_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.049
Feature: Using Tor bridges and pluggable transports
45.310
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 28.869
And I capture all network traffic 0.371
When the network is plugged 16.069
Command 
Command failed (pid 11267 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/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:176: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 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 13.656 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:43:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:43:49_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:43:49_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_20267-webtunnel/5/artifact/build-artifacts/00:43:49_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:43:49_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:43:49_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/00:43:49_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.054
Feature: Packages are up-to-date
Tags: @source
11.914
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 11.914
Command 
Command failed (pid 49131 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/tmp/tails-amd64-20267-webtunnel@83d53bdbf8+stable@9f98e6d92e-20250714T1635Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/tmp/tails-amd64-20267-webtunnel@83d53bdbf8+stable@9f98e6d92e-20250714T1635Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - b43-fwcutter (1:019-8tails1) to Debian trixie (1:019-13)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20267-webtunnel/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
21:31.879
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 10.181
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 7.920
And Tails detects disk read failures on the boot device 1.679
When I try to enable persistence 0.433
Then the Welcome Screen tells me that my hardware is probably failing 21.780
When I log in to a new session 49.749
And all notifications have disappeared 20:0.135
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:724:in `new'
./features/step_definitions/common_steps.rb:724:in `/^all notifications have disappeared$/'
features/persistence.feature:212:in `And all notifications have disappeared'
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 10.843 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:57:47)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/04:57:47_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/04:57:47_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/04:57:47_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product @doc
1:43.546
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.334
And I capture all network traffic 0.009
When I successfully start the Unsafe Browser 18.963
And I open the Tails homepage in the Unsafe Browser 11.928
And the Tails homepage loads in the Unsafe Browser 1:0.310
cannot 
cannot find TailsHomepage.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/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:21:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.455 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:20:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:20:20_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:20:20_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:20:20_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:20:20_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.060
Feature: Browsing the web using the Unsafe Browser
Tags: @product @doc
1:43.009
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.245
When I successfully start the Unsafe Browser 19.064
When I open the Tails homepage in the Unsafe Browser 10.218
Then the Tails homepage loads in the Unsafe Browser 1:0.480
cannot 
cannot find TailsHomepage.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/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:39:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 5.506 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 05:52:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:52:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:52:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:52:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/05:52:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
32.784
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 23.398
And I unlock and mount this VeraCrypt file container with GNOME Disks 9.386
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.455 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 06:03:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/06:03:19_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/06:03:19_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/06:03:19_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20267-webtunnel/5/artifact/build-artifacts/06:03:19_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014