Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 8 23 Jun 2025, 22:01

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
38.933
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:509 0.011
Steps
Given I have started Tails from DVD without network and logged in 15.217
When the network is plugged 23.715
Command 
Command failed (pid 7073 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.076
After features/support/hooks.rb:330 6.585 
SCENARIO FAILED: 'Clock with host's time' (at time 00:17:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:17_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:17_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/8/artifact/build-artifacts/00:17:17_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:17_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:17_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:17_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
31.302
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Before features/support/hooks.rb:509 0.028
Steps
Given I have started Tails from DVD without network and logged in 20.770
When the network is plugged 10.532
Command 
Command failed (pid 7240 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.050
After features/support/hooks.rb:330 6.201 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:17:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:56_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/8/artifact/build-artifacts/00:17:56_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/8/artifact/build-artifacts/00:17:56_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/8/artifact/build-artifacts/00:17:56_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:17:56_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/8/artifact/build-artifacts/00:17:56_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
1:15.706
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 45.407
When I bump the system time with "+1 day" 3.990
And I capture all network traffic 0.185
And the network is plugged 26.123
Command 
Command failed (pid 7771 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.031
After features/support/hooks.rb:330 7.074 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:19:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:19:18_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/8/artifact/build-artifacts/00:19:18_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/8/artifact/build-artifacts/00:19:18_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/8/artifact/build-artifacts/00:19:18_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/8/artifact/build-artifacts/00:19:18_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/8/artifact/build-artifacts/00:19:18_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.050
Feature: Time syncing
Tags: @product @check_tor_leaks
37.525
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.004
Steps
Given I have started Tails from DVD without network and logged in 11.119
And I make sure time sync before Tor connects times out 2.743
When the network is plugged 23.662
Command 
Command failed (pid 9010 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.043
After features/support/hooks.rb:330 6.177 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:27:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:27:35_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/8/artifact/build-artifacts/00:27:35_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/8/artifact/build-artifacts/00:27:35_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/8/artifact/build-artifacts/00:27:35_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/8/artifact/build-artifacts/00:27:35_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/8/artifact/build-artifacts/00:27:35_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
50.848
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 25.409
When I bump the system time with "+8 hours +15 minutes" 1.302
And all notifications have disappeared 10.740
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.293
And the network is plugged 13.098
Command 
Command failed (pid 9265 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.033
After features/support/hooks.rb:330 6.507 
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:28:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:28:34_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/8/artifact/build-artifacts/00:28:34_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/8/artifact/build-artifacts/00:28:34_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/8/artifact/build-artifacts/00:28:34_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/8/artifact/build-artifacts/00:28:34_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/8/artifact/build-artifacts/00:28:34_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.042
Feature: Time syncing
Tags: @product @check_tor_leaks
52.997
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:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 25.648
When I bump the system time with "+8 hours +15 minutes" 1.223
And all notifications have disappeared 12.663
And I capture all network traffic 0.004
And the network is plugged 13.458
Command 
Command failed (pid 9527 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.043
After features/support/hooks.rb:330 6.724 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:29:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:29:34_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/8/artifact/build-artifacts/00:29:34_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/8/artifact/build-artifacts/00:29:34_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/8/artifact/build-artifacts/00:29:34_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/8/artifact/build-artifacts/00:29:34_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/8/artifact/build-artifacts/00:29:34_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.040
Feature: Time syncing
Tags: @product @check_tor_leaks
56.358
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 27.387
And I make sure time sync before Tor connects uses a fake connectivity check service 3.924
And the network is plugged 25.047
Command 
Command failed (pid 9791 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.048
After features/support/hooks.rb:330 6.120 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:30:37)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:30:37_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/8/artifact/build-artifacts/00:30:37_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/8/artifact/build-artifacts/00:30:37_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/8/artifact/build-artifacts/00:30:37_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/8/artifact/build-artifacts/00:30:37_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/8/artifact/build-artifacts/00:30:37_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:17.147
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 1:4.999
And I capture all network traffic 0.035
When the network is plugged 12.112
Command 
Command failed (pid 10268 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 9.458 
SCENARIO FAILED: 'Using normal bridges' (at time 00:32:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:00_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
26.424
Background
Before features/support/hooks.rb:266 0.014
Before features/support/hooks.rb:273 0.059
Steps
Given I have started Tails from DVD without network and logged in 15.519
And I capture all network traffic 0.007
When the network is plugged 10.897
Command 
Command failed (pid 10425 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.333 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:32:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:36_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:36_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/8/artifact/build-artifacts/00:32:36_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:36_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:36_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:32:36_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
33.276
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 17.490
And I capture all network traffic 0.002
When the network is plugged 15.783
Command 
Command failed (pid 10578 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 6.275 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:33:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:33: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/8/artifact/build-artifacts/00:33: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/8/artifact/build-artifacts/00:33: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/8/artifact/build-artifacts/00:33: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/8/artifact/build-artifacts/00:33: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/8/artifact/build-artifacts/00:33:16_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.057
Feature: Using Tor bridges and pluggable transports
54.020
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 30.857
And I capture all network traffic 0.022
When the network is plugged 23.141
Command 
Command failed (pid 10831 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 6.193 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:34:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:34:17_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/8/artifact/build-artifacts/00:34:17_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:34:17_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/8/artifact/build-artifacts/00:34:17_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/8/artifact/build-artifacts/00:34:17_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/8/artifact/build-artifacts/00:34:17_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
58.935
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 44.373
And I capture all network traffic 0.235
When the network is plugged 14.326
Command 
Command failed (pid 11189 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 9.615 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:35:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:35:22_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.038
Feature: Using Tor bridges and pluggable transports
1:24.907
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 1:0.263
And I capture all network traffic 0.021
When the network is plugged 24.623
Command 
Command failed (pid 11562 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.104 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:36:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:36:57_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/8/artifact/build-artifacts/00:36:57_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/8/artifact/build-artifacts/00:36:57_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/8/artifact/build-artifacts/00:36:57_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/8/artifact/build-artifacts/00:36:57_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/8/artifact/build-artifacts/00:36:57_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
1:14.392
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 45.048
And I capture all network traffic 0.213
When the network is plugged 29.129
Command 
Command failed (pid 11927 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 6.184 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:38:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:38:17_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/8/artifact/build-artifacts/00:38:17_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/8/artifact/build-artifacts/00:38:17_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:38:17_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:38:17_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:38:17_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.031
Feature: Using Tor bridges and pluggable transports
59.803
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 44.748
And I capture all network traffic 0.160
When the network is plugged 14.894
Command 
Command failed (pid 12289 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 15.440 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:39:26)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:39:26_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/8/artifact/build-artifacts/00:39:26_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/8/artifact/build-artifacts/00:39:26_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/8/artifact/build-artifacts/00:39:26_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:39:26_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/8/artifact/build-artifacts/00:39:26_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:100 0.038
Feature: Using Tor bridges and pluggable transports
43.842
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 29.039
And I capture all network traffic 0.229
When the network is plugged 14.573
Command 
Command failed (pid 12546 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 13.735 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:40:26)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:40:26_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/8/artifact/build-artifacts/00:40:26_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/8/artifact/build-artifacts/00:40:26_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/8/artifact/build-artifacts/00:40:26_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/8/artifact/build-artifacts/00:40:26_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/8/artifact/build-artifacts/00:40:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
24.965
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Steps
Given I have started Tails from DVD without network and logged in 10.400
And I capture all network traffic 0.081
When the network is plugged 14.483
Command 
Command failed (pid 12697 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 10.194 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:41:02)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:41:02_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/8/artifact/build-artifacts/00:41:02_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/8/artifact/build-artifacts/00:41:02_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/8/artifact/build-artifacts/00:41:02_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/8/artifact/build-artifacts/00:41:02_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/8/artifact/build-artifacts/00:41:02_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.054
Feature: Using Tor bridges and pluggable transports
25.098
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails from DVD without network and logged in 13.515
And I capture all network traffic 0.011
When the network is plugged 11.570
Command 
Command failed (pid 12849 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 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 6.849 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:41:37)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:41:37_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_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:41:37_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/8/artifact/build-artifacts/00:41:37_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:41:37_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/00:41:37_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/8/artifact/build-artifacts/00:41:37_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.051
Feature: Installing Tails to a USB drive
Tags: @product @not_release_blocker
1:16.375
Scenario Try installing Tails to a too small USB drive with GPT and a FAT partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.058
Steps
Given I have started Tails from DVD without network and logged in 27.741
And I temporarily create a 4 GiB disk named "gptfat" 0.603
And I create a gpt partition with a vfat filesystem on disk "gptfat" 15.365
And I plug USB drive "gptfat" 7.846
When I start Tails Installer 24.818
cannot 
cannot find TailsClonerWindow.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/usb.rb:156:in `/^I start Tails Installer$/'
features/usb_install.feature:12:in `When I start Tails Installer'
Then I am told by Tails Installer that the destination device "is too small" 0.000
After features/support/hooks.rb:330 5.845 
SCENARIO FAILED: 'Try installing Tails to a too small USB drive with GPT and a FAT partition' (at time 01:20:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:20:18_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:20:18_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:20:18_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:20:18_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.journal
After features/support/hooks.rb:100 0.001
Feature: Installing Tails to a USB drive
Tags: @product
1:22.960
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.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.960
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: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 6.672 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:30:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:30:36_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/8/artifact/build-artifacts/01:30:36_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/8/artifact/build-artifacts/01:30:36_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/8/artifact/build-artifacts/01:30:36_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:27.930
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:27.930
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:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I have started Tails from DVD without network and logged in 0.000
And I clone USB drive "__internal" to a temporary USB drive "install" 0.000
And I plug USB drive "install" 0.000
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall 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 6.680 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 01:36:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:36:37_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:36:37_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:36:37_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/01:36:37_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:20.969
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:20.969
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_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 6.983 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:58:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/02:58:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/02:58:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/02:58:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/02:58:17_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:13.973
Scenario Tails erases memory on DVD boot medium removal: vfat
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:13.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\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/emergency_shutdown.feature:26:in `Given I have started Tails from DVD without network and logged in'
And I prepare Tails for memory erasure tests 0.000
And I plug and mount a 128 MiB USB drive with a vfat filesystem 0.000
And I fill the USB drive with a known pattern 0.000
And I read the content of the test FS 0.000
And patterns cover at least 90% of the test FS size in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 5.456 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:04:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:04:17_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:04:17_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:04:17_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:04:17_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
2:54.832
Scenario Using Tails' custom backup tool to backup a newly added file
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 enabled and logged in 1:13.799
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 19.153
And I clone USB drive "__internal" to a temporary USB drive "backup" 7.123
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.755
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/backup.feature:12:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 6.350 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:14:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:14:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:14:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:14:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:14:34_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.177
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
1:27.065
Scenario The Tails documentation launcher works when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.061
Steps
Given I have started Tails from DVD and logged in and the network is connected 28.136
When I start "Tails Documentation" via GNOME Activities Overview 11.351
Then the Tor Browser has started 47.577
cannot 
cannot find TorBrowserNewTabButton.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:468:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:13:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 11.467 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 03:20:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:20:39_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:20:39_The_Tails_documentation_launcher_works_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:20:39_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:20:39_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product
1:15.773
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.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.773
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 7.139 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 03:25:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:25:54_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/8/artifact/build-artifacts/03:25:54_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/8/artifact/build-artifacts/03:25:54_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/8/artifact/build-artifacts/03:25:54_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
1:11.906
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:11.906
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:54: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/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 7.298 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 03:27:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:27:14_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:27:14_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:27:14_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:27:14_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
1:15.351
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.351
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/gnome.feature:22:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 0.000
And Tor is ready 0.000
And all notifications have disappeared 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I close the "tails-additional-software-config" window 0.000
When I start "Disks" via GNOME Activities Overview 0.000
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 0.000
When I start "GNOME Terminal" via GNOME Activities Overview 0.000
And I close the "gnome-terminal-server" window 0.000
When I start "Files" via GNOME Activities Overview 0.000
And I close the "org.gnome.Nautilus" window 0.000
When I start "Persistent Storage" via GNOME Activities Overview 0.000
And I close the "tps-frontend" window 0.000
When I start "Persistent Storage Backup" via GNOME Activities Overview 0.000
And I close the "zenity" window 0.000
When I start "Pidgin" via GNOME Activities Overview 0.000
And I close the "Pidgin" window via Alt+F4 0.000
When I start "Thunderbird" via GNOME Activities Overview 0.000
And I close the "Thunderbird" window 0.000
When I start "Tor Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000
And I close the "unlock-veracrypt-volumes" window 0.000
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
After features/support/hooks.rb:330 6.996 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 03:30:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:30:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:30:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:30:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:30:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
32.293
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given a computer 0.345
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.437
When Tails detects disk read failures on the SquashFS 1.493
Then I see a disk failure message 10.017
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 5.846 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 03:34:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:34:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:34:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:34:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:34:35_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:16.580
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.329
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.251
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/hardware_failure.feature:30:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 7.208 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:35:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:35:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:35:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:35:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:35:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product
4:18.529
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.298
And I set Tails to boot with options "test_partitioning_errors=guid" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.098
And I plug USB drive "temp" 1.107
And I write the Tails USB image to disk "temp" 1:1.237
When I start Tails from USB drive "temp" with network unplugged 3:15.787
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/hardware_failure.feature:80:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error guid-not-randomized 0.000
After features/support/hooks.rb:330 14.385 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#1)' (at time 03:53:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:53:39_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:53:39_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/03:53:39_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.528
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product @doc
1:17.610
Scenario The included OpenPGP keys are up-to-date
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:17.610
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/keys.feature:6:in `Given I have started Tails from DVD without network and logged in'
Then the included OpenPGP keys are valid for the next 1 month 0.000
After features/support/hooks.rb:330 5.456 
SCENARIO FAILED: 'The included OpenPGP keys are up-to-date' (at time 04:03:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:03:57_The_included_OpenPGP_keys_are_up-to-date.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:03:57_The_included_OpenPGP_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:03:57_The_included_OpenPGP_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:03:57_The_included_OpenPGP_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
1:11.426
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD without network and logged in 1:11.426
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/keys.feature:10:in `Given I have started Tails from DVD without network and logged in'
Then the keys trusted by APT are valid for the next 3 months 0.000
After features/support/hooks.rb:330 5.555 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:05:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:05:15_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:05:15_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:05:15_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:05:15_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:8.858
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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.081
When I log in to a new session in Russian (ru) 46.144
Then the keyboard layout is set to "ru" 0.242
When the network is plugged 0.078
And Tor is ready 11.310
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 5.665 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:54:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/8/artifact/build-artifacts/04:54:10_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/8/artifact/build-artifacts/04:54:10_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/8/artifact/build-artifacts/04:54:10_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/8/artifact/build-artifacts/04:54:10_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
9.133
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:534 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 9.133
Command 
Command failed (pid 51252 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/tmp/tails-amd64-21027-fix-interactive-debugging-context@344e8364c9+stable@d88a397cbb-20250623T1353Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/tmp/tails-amd64-21027-fix-interactive-debugging-context@344e8364c9+stable@d88a397cbb-20250623T1353Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - ublock-origin (1.62.0+dfsg-1) to Debian trixie (1.62.0+dfsg-2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:541 0.000
After features/support/hooks.rb:100 0.000