Project Number Date
test_Tails_ISO_feature-arti 92 17 Jun 2025, 16:44

Failures Overview

The following summary displays scenarios that failed.

Feature: Root access control enforcement
Tags: @product
2:51.734
Scenario If cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen
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 2:51.734
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/root_access_control.feature:13:in `Given I have started Tails from DVD without network and logged in'
And running a command as root with pkexec requires PolicyKit administrator privileges 0.000
Then I cannot run a command as root with sudo and the standard passwords 0.000
And I cannot run a command as root with pkexec and the standard passwords 0.000
Then I cannot login as root using su with the standard passwords 0.000
After features/support/hooks.rb:330 6.920 
SCENARIO FAILED: 'If cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen' (at time 00:20:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:20:46_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:20:46_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:20:46_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:20:46_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
38.618
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.006
Steps
Given I have started Tails from DVD without network and logged in 16.006
When the network is plugged 22.612
Command 
Command failed (pid 5749 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.037
After features/support/hooks.rb:330 8.938 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:21:31_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:27.149
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:27.149
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/time_syncing.feature:14:in `Given I have started Tails from DVD without network and logged in'
When the network is plugged 0.000
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.047
After features/support/hooks.rb:330 6.280 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:23:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:08_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:08_Clock_with_host_s_time_while_using_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:08_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:08_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
32.187
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.002
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 19.806
When I bump the system time with "+1 day" 0.397
And I capture all network traffic 0.004
And the network is plugged 11.979
Command 
Command failed (pid 6382 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.042
After features/support/hooks.rb:330 7.599 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:23:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:23:46_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.044
Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
1:11.980
Scenario The system time is not synced to the hardware clock
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 1:11.980
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/time_syncing.feature:34:in `Given I have started Tails from DVD without network and logged in'
When I bump the system time with "-15 days" 0.000
And I warm reboot the computer 0.000
And the computer reboots Tails 0.000
Then Tails' hardware clock is close to the host system's time 0.000
After features/support/hooks.rb:517 0.032
After features/support/hooks.rb:330 6.756 
SCENARIO FAILED: 'The system time is not synced to the hardware clock' (at time 00:25:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:25:06_The_system_time_is_not_synced_to_the_hardware_clock.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:25:06_The_system_time_is_not_synced_to_the_hardware_clock.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:25:06_The_system_time_is_not_synced_to_the_hardware_clock.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:25:06_The_system_time_is_not_synced_to_the_hardware_clock.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:10.902
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.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 1:10.902
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/time_syncing.feature:56:in `Given I have started Tails from DVD without network and logged in'
And I make sure time sync before Tor connects times out 0.000
When the network is plugged 0.000
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.040
After features/support/hooks.rb:330 7.127 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:31:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:31:45_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_feature-arti/92/artifact/build-artifacts/00:31:45_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:31:45_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_feature-arti/92/artifact/build-artifacts/00:31:45_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
1:17.029
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.009
Before features/support/hooks.rb:509 0.010
Steps
Given I have started Tails from DVD without network and logged in 33.733
When I bump the system time with "+8 hours +15 minutes" 0.479
And all notifications have disappeared 7.470
And I capture all network traffic 0.004
And I make sure time sync before Tor connects fails 0.166
And the network is plugged 35.176
Command 
Command failed (pid 8377 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/time_syncing.feature:68:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 0.000
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 6.126 
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:33:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:33:09_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.040
Feature: Time syncing
Tags: @product @check_tor_leaks
1:17.379
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.003
Steps
Given I have started Tails from DVD without network and logged in 1:17.379
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/time_syncing.feature:83:in `Given I have started Tails from DVD without network and logged in'
When I bump the system time with "+8 hours +15 minutes" 0.000
And all notifications have disappeared 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
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.034
After features/support/hooks.rb:330 5.712 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:34:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:34:32_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:34:32_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:34:32_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:34:32_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.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:18.401
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.003
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 44.983
And I make sure time sync before Tor connects uses a fake connectivity check service 6.276
And the network is plugged 27.141
Command 
Command failed (pid 9227 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.049
After features/support/hooks.rb:330 11.136 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:35:57)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1750156726/002auth/diff-cache/1104
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:35:57_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_feature-arti/92/artifact/build-artifacts/00:35:57_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_feature-arti/92/artifact/build-artifacts/00:35:57_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_feature-arti/92/artifact/build-artifacts/00:35:57_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_feature-arti/92/artifact/build-artifacts/00:35:57_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_feature-arti/92/artifact/build-artifacts/00:35:57_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.027
Feature: Using Tor bridges and pluggable transports
28.102
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.113
Steps
Given I have started Tails from DVD without network and logged in 13.922
And I capture all network traffic 0.296
When the network is plugged 13.883
Command 
Command failed (pid 9385 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 12.587 
SCENARIO FAILED: 'Using normal bridges' (at time 00:36:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:36:36_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.062
Feature: Using Tor bridges and pluggable transports
22.265
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.047
Steps
Given I have started Tails from DVD without network and logged in 11.268
And I capture all network traffic 0.003
When the network is plugged 10.992
Command 
Command failed (pid 9540 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.197 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:37:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:37:11_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.052
Feature: Using Tor bridges and pluggable transports
1:18.217
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 1:4.880
And I capture all network traffic 0.102
When the network is plugged 13.233
Command 
Command failed (pid 10019 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 12.068 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:38:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:38:36_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
24.825
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails from DVD without network and logged in 11.975
And I capture all network traffic 0.003
When the network is plugged 12.846
Command 
Command failed (pid 10178 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.749 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:39:13)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:13_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.066
Feature: Using Tor bridges and pluggable transports
30.327
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 20.079
And I capture all network traffic 0.004
When the network is plugged 10.243
Command 
Command failed (pid 10331 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
0.000
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.149 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:39:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:39:50_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
1:0.565
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 47.692
And I capture all network traffic 0.275
When the network is plugged 12.598
Command 
Command failed (pid 10694 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 10.565 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:40:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:40: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_feature-arti/92/artifact/build-artifacts/00:40: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_feature-arti/92/artifact/build-artifacts/00:40: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_feature-arti/92/artifact/build-artifacts/00:40: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_feature-arti/92/artifact/build-artifacts/00:40: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_feature-arti/92/artifact/build-artifacts/00:40:57_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.060
Feature: Using Tor bridges and pluggable transports
48.951
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 16.235
And I capture all network traffic 0.417
When the network is plugged 32.297
Command 
Command failed (pid 10851 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given the Tor network and default bridges are unblocked 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 12.983 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:41:57)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1750156726/012relay/diff-cache/1171
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:41:57_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.055
Feature: Using Tor bridges and pluggable transports
45.563
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.092
Steps
Given I have started Tails from DVD without network and logged in 14.043
And I capture all network traffic 0.368
When the network is plugged 31.150
Command 
Command failed (pid 11007 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 9.063 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:42:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:42:56_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
32.946
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 16.892
And I capture all network traffic 0.130
When the network is plugged 15.923
Command 
Command failed (pid 11162 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 15.525 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:43:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:43:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:43:42_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_feature-arti/92/artifact/build-artifacts/00:43:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:43:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:43:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:43:42_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.056
Feature: Using Tor bridges and pluggable transports
44.250
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 27.047
And I capture all network traffic 0.012
When the network is plugged 17.189
Command 
Command failed (pid 11418 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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 16.114 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:44:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:44:42_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_feature-arti/92/artifact/build-artifacts/00:44:42_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_feature-arti/92/artifact/build-artifacts/00:44:42_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:44:42_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:44:42_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:44:42_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
40.091
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 28.494
And I capture all network traffic 0.011
When the network is plugged 11.585
Command 
Command failed (pid 11674 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186: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.778 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:45:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/00:45:34_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.038
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
7:4.416
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.050
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:4.416
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 5.352 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:01:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:01:10_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:01:10_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:01:10_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:01:10_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow
1:38.202
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.005
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:38.202
Command 
Command failed (pid 17943 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/common_steps.rb:324:in `/^I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login$/'
features/additional_software_packages.feature:28:in `Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login'
And I update APT using apt 0.000
And I install "popularity-contest" using apt 0.000
Then I am proposed to add the "popularity-contest" package to my Additional Software 0.000
When I create a persistent storage and activate the Additional Software feature 0.000
Then Additional Software is correctly configured for package "popularity-contest" 0.000
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 7.957 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:57:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails_chutney-data
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:57:31_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:16.159
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Before features/support/hooks.rb:509 0.010
Steps
Given a computer 1.011
And I start Tails from USB drive "__internal" and I login with an administration password 2:15.148
Command 
Command failed (pid 18130 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/common_steps.rb:299:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update APT using apt 0.000
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 12.098 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:59:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package_chutney-data
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/01:59:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.054
Feature: Additional software
Tags: @product @check_tor_leaks @slow
1:59.930
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Before features/support/hooks.rb:509 0.025
Steps
Given a computer 1.743
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:58.186
Command 
Command failed (pid 18321 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/common_steps.rb:299:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:517 0.031
After features/support/hooks.rb:330 6.626 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:02:08)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic_chutney-data
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:02:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
1:58.773
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.003
Steps
Given a computer 0.297
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:58.475
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:471: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:470:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:295: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:470:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:517 0.040
After features/support/hooks.rb:330 6.130 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:04:13)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:04:13_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
1:54.715
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.003
Steps
Given a computer 1.103
And I start Tails from USB drive "__internal" with network unplugged 1:36.631
And I enable persistence 16.981
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:517 0.030
After features/support/hooks.rb:330 6.264 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:06:15)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:06:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:4.927
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.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 39.349
And no SquashFS delta is installed 0.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.246
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.001
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.801
When the network is plugged 21.556
Command 
Command failed (pid 20971 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/usb_upgrade.feature:88:in `When the network is plugged'
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 3:37.987 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:26:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_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_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
43.267
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.391
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.991
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.651
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 22.355
Command 
Command failed (pid 21134 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/usb_upgrade.feature:132:in `When the network is plugged'
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 6.862 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:31:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
49.603
Scenario Tails shuts down on DVD boot medium removal
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD and logged in and the network is connected 49.603
Command 
Command failed (pid 21288 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/emergency_shutdown.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
When I eject the boot medium 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 6.081 
SCENARIO FAILED: 'Tails shuts down on DVD boot medium removal' (at time 02:32:08)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:32:08_Tails_shuts_down_on_DVD_boot_medium_removal.journal
After features/support/hooks.rb:100 0.000
Feature: Getting a DHCP lease without leaking too much information
55.577
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 14.051
And I capture all network traffic 0.043
And the network is plugged 41.481
Command 
Command failed (pid 26338 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/dhcp.feature:11:in `And the network is plugged'
And Tor is ready 0.000
And all notifications have disappeared 0.000
And available upgrades have been checked 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.000
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:330 5.910 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 02:43:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:10_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.040
Feature: Getting a DHCP lease without leaking too much information
33.930
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 11.604
And I capture all network traffic 0.007
And the network is plugged 22.317
Command 
Command failed (pid 26489 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/dhcp.feature:11:in `And the network is plugged'
And Tor is ready 0.000
And all notifications have disappeared 0.000
And available upgrades have been checked 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.000
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.000
And I switch to the "manually-added-con" NetworkManager connection 0.000
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:330 6.420 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 02:43:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:43:50_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.048
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
54.161
Scenario The Tails documentation launcher works when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 54.161
Command 
Command failed (pid 26829 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/documentation.feature:11:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start "Tails Documentation" via GNOME Activities Overview 0.000
Then the Tor Browser has started 0.000
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 6.054 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 02:45:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:45:51_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
27.310
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.014
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 16.397
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 10.912
Command 
Command failed (pid 28471 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/gnome.feature:24:in `And the network is plugged'
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 7.022 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:50:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:50:28_I_can_launch_various_apps_via_GNOME_Activities_Overview_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:50:28_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_feature-arti/92/artifact/build-artifacts/02:50:28_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:50:28_I_can_launch_various_apps_via_GNOME_Activities_Overview.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:50:28_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:50:28_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:6.651
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.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 15.285
When I log in to a new session in Arabic (ar) 40.816
Then the keyboard layout is set to "us" 0.181
When the network is plugged 10.368
Command 
Command failed (pid 34298 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:44:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 9.389 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 03:22:06)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:22:06_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:36.373
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 23.998
When I log in to a new session in Chinese (zh_CN) 51.221
Then the keyboard layout is set to "cn" 0.468
When the network is plugged 20.684
Command 
Command failed (pid 34758 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:45:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 5.953 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:23:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:23:50_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
48.527
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.099
When I log in to a new session in English (en) 25.798
Then the keyboard layout is set to "us" 0.178
When the network is plugged 11.450
Command 
Command failed (pid 35074 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:46:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.751 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 03:24:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:24:46_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:14.345
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.281
When I log in to a new session in French (fr) 54.517
Then the keyboard layout is set to "fr" 0.382
When the network is plugged 11.162
Command 
Command failed (pid 35395 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:47:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
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 "fr" 0.000
After features/support/hooks.rb:330 6.292 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 03:26:06)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:26:06_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:10.736
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 9.157
When I log in to a new session in German (de) 51.084
Then the keyboard layout is set to "de" 0.141
When the network is plugged 10.352
Command 
Command failed (pid 35728 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:48:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
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 "de" 0.000
After features/support/hooks.rb:330 8.345 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 03:27:24)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:27:24_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:13.697
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.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.862
When I log in to a new session in Italian (it) 52.360
Then the keyboard layout is set to "it" 0.257
When the network is plugged 12.216
Command 
Command failed (pid 36049 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:52:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 7.600 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 03:28:47)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:28:47_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:13.258
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.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.169
When I log in to a new session in Persian (fa) 50.412
Then the keyboard layout is set to "ir" 0.227
When the network is plugged 12.448
Command 
Command failed (pid 36372 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:53:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
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 "ir" 0.000
After features/support/hooks.rb:330 6.524 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 03:30:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:30:07_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:11.788
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.581
When I log in to a new session in Portuguese (pt) 50.018
Then the keyboard layout is set to "pt" 0.146
When the network is plugged 12.042
Command 
Command failed (pid 36704 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:54:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.600 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 03:31:25)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:31:25_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:15.770
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.684
When I log in to a new session in Russian (ru) 53.422
Then the keyboard layout is set to "ru" 0.348
When the network is plugged 13.315
Command 
Command failed (pid 37016 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:55:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ru" 0.000
After features/support/hooks.rb:330 6.040 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 03:32:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:32:48_Tails_is_localized_for_every_tier-1_language,_Examples___9__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:32:48_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_feature-arti/92/artifact/build-artifacts/03:32:48_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:32:48_Tails_is_localized_for_every_tier-1_language,_Examples___9_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:32:48_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:32:48_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:11.995
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.169
When I log in to a new session in Spanish (es) 51.388
Then the keyboard layout is set to "es" 0.301
When the network is plugged 11.135
Command 
Command failed (pid 37329 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:56:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 7.456 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 03:34:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:34:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:14.139
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.623
When I log in to a new session in Turkish (tr) 50.235
Then the keyboard layout is set to "tr" 0.277
When the network is plugged 13.003
Command 
Command failed (pid 37653 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/localization.feature:57:in `When the network is plugged'
features/localization.feature:25:in `When the network is plugged'
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.448 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 03:35:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11__chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11_.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:35:28_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
1:11.958
Scenario MAC address spoofing is disabled
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 stopped at Tails Greeter's login screen 24.695
And I capture all network traffic 0.006
When I disable MAC spoofing in Tails Greeter 11.569
And I log in to a new session 25.210
And the network is plugged 10.476
Command 
Command failed (pid 38085 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/mac_spoofing.feature:13:in `And the network is plugged'
And Tor is ready 0.000
Then 1 network interface is enabled 0.000
And the 1st network device has its real MAC address configured 0.000
When I hotplug a network device and wait for it to be initialized 0.000
Then 2 network interfaces are enabled 0.000
And the 2nd network device has its real MAC address configured 0.000
And some network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 6.635 
SCENARIO FAILED: 'MAC address spoofing is disabled' (at time 03:36:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:36:46_MAC_address_spoofing_is_disabled.journal
After features/support/hooks.rb:100 0.064
Feature: Spoofing MAC addresses
Tags: @product
1:37.726
Scenario MAC address spoofing is successful
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 stopped at Tails Greeter's login screen 8.545
And I capture all network traffic 0.070
When I log in to a new session 30.999
And the network is plugged 58.111
Command 
Command failed (pid 38425 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/mac_spoofing.feature:26:in `And the network is plugged'
And Tor is ready 0.000
Then 1 network interface is enabled 0.000
And the 1st network device has a spoofed MAC address configured 0.000
When I hotplug a network device and wait for it to be initialized 0.000
Then 2 network interfaces are enabled 0.000
And the 2nd network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 5.632 
SCENARIO FAILED: 'MAC address spoofing is successful' (at time 03:38:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:38:31_MAC_address_spoofing_is_successful.journal
After features/support/hooks.rb:100 0.048
Feature: Spoofing MAC addresses
Tags: @product
49.729
Scenario MAC address spoofing fails and macchanger returns false
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.078
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 15.487
And I capture all network traffic 0.004
And the network is plugged 34.237
Command 
Command failed (pid 38584 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/mac_spoofing.feature:38:in `And the network is plugged'
And macchanger will fail by not spoofing and always returns false 0.000
When I log in to a new session 0.000
Then no network interfaces are enabled 0.000
And no network device leaked the real MAC address 0.000
And I see the "Wired Network Disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:330 7.017 
SCENARIO FAILED: 'MAC address spoofing fails and macchanger returns false' (at time 03:39:27)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:27_MAC_address_spoofing_fails_and_macchanger_returns_false.journal
After features/support/hooks.rb:100 0.052
Feature: Spoofing MAC addresses
Tags: @product
20.286
Scenario MAC address spoofing fails and macchanger returns true
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 stopped at Tails Greeter's login screen 9.738
And I capture all network traffic 0.020
And the network is plugged 10.527
Command 
Command failed (pid 38734 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/mac_spoofing.feature:48:in `And the network is plugged'
And macchanger will fail by not spoofing and always returns true 0.000
When I log in to a new session 0.000
Then no network interfaces are enabled 0.000
And no network device leaked the real MAC address 0.000
And I see the "Wired Network Disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:330 6.223 
SCENARIO FAILED: 'MAC address spoofing fails and macchanger returns true' (at time 03:39:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:39:54_MAC_address_spoofing_fails_and_macchanger_returns_true.journal
After features/support/hooks.rb:100 0.050
Feature: Spoofing MAC addresses
Tags: @product
27.540
Scenario MAC address spoofing fails and the module is not removed
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 stopped at Tails Greeter's login screen 14.691
And I capture all network traffic 0.005
And the network is plugged 12.844
Command 
Command failed (pid 38886 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/mac_spoofing.feature:58:in `And the network is plugged'
And macchanger will fail by not spoofing and always returns true 0.000
And no network interface modules can be unloaded 0.000
When I log in to a new session 0.000
Then 1 network interface is enabled 0.000
But the MAC spoofing panic mode disabled networking 0.000
And no network device leaked the real MAC address 0.000
And I see the "All Networking Disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:330 6.043 
SCENARIO FAILED: 'MAC address spoofing fails and the module is not removed' (at time 03:40:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:40:28_MAC_address_spoofing_fails_and_the_module_is_not_removed.journal
After features/support/hooks.rb:100 0.037
Feature: Networking
Tags: @product
1:7.767
Scenario No initial network
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 16.276
And I wait between 30 and 60 seconds 40.040 
Slept for 40 seconds
Then the Tor Status icon tells me that Tor is not usable 1.001
When the network is plugged 10.448
Command 
Command failed (pid 39549 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/networking.feature:8:in `When the network is plugged'
Then I successfully configure Tor 0.000
And the Tor Status icon tells me that Tor is usable 0.000
And all notifications have disappeared 0.000
And the time has synced 0.000
After features/support/hooks.rb:330 6.157 
SCENARIO FAILED: 'No initial network' (at time 03:45:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:45:48_No_initial_network.journal
After features/support/hooks.rb:100 0.000
Feature: Onion Circuits
Tags: @product
22.013
Scenario Onion Circuits shows some circuits
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 22.013
Command 
Command failed (pid 40025 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/onioncircuits.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start "Onion Circuits" via GNOME Activities Overview 0.000
Then Onion Circuits starts 0.000
And Onion Circuits shows some circuits 0.000
After features/support/hooks.rb:330 5.851 
SCENARIO FAILED: 'Onion Circuits shows some circuits' (at time 03:47:08)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:47:08_Onion_Circuits_shows_some_circuits.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:39.857
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 2:39.857
Command 
Command failed (pid 40501 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update APT using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:330 6.409 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 03:49:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/03:49:54_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
30.241
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.011
And the network is plugged 10.230
Command 
Command failed (pid 43280 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/persistence.feature:74:in `And the network is plugged'
And Tor is ready 0.000
And I take note of which tps features are available 0.000
When I write some files expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 7.478 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:04:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:04:28_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
54.434
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.007
And the network is plugged 38.427
Command 
Command failed (pid 43429 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/persistence.feature:84:in `And the network is plugged'
And Tor is ready 0.000
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 7.726 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:05:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:05:30_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:13.742
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 13.181
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.141
When I try to enable persistence 0.410
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.008
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 15.473 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:43:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:33.436
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 15.526
And I create a persistent partition with the default settings 35.614
Then the "TorConfiguration" tps feature is not enabled 5.402
When the network is plugged 36.893
Command 
Command failed (pid 50061 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/persistent_tor_bridges.feature:11:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 7.124 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:48:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:48:28_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:15.708
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 16.986
And I create a persistent partition with the default settings 43.650
Then the "TorConfiguration" tps feature is not enabled 3.747
When the network is plugged 11.324
Command 
Command failed (pid 50213 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/persistent_tor_bridges.feature:11:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 7.170 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:49:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:49:51_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
40.815
Scenario No unexpected network services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 40.815
Command 
Command failed (pid 50998 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/sane_defaults.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
Then no unexpected services are listening for network connections 0.000
After features/support/hooks.rb:330 8.615 
SCENARIO FAILED: 'No unexpected network services' (at time 04:55:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:55:56_No_unexpected_network_services.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
26.499
Scenario The live user can only access the expected local services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.036
Steps
Given I have started Tails from DVD and logged in and the network is connected 26.499
Command 
Command failed (pid 51153 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/sane_defaults.feature:16:in `Given I have started Tails from DVD and logged in and the network is connected'
Then the live user can only access allowed local services 0.000
After features/support/hooks.rb:330 6.398 
SCENARIO FAILED: 'The live user can only access the expected local services' (at time 04:56:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:56:31_The_live_user_can_only_access_the_expected_local_services.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
25.524
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 25.524
Command 
Command failed (pid 51694 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/shutdown_applet.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
When I request a shutdown using the system menu 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 10.452 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 04:57:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:57:57_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
26.323
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD and logged in and the network is connected 26.323
Command 
Command failed (pid 51844 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/shutdown_applet.feature:11:in `Given I have started Tails from DVD and logged in and the network is connected'
When I request a reboot using the system menu 0.000
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 6.779 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 04:58:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:58:33_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
28.005
Background
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 and logged in and the network is connected 28.005
Command 
Command failed (pid 51997 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/ssh.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Logging in via SSH
Tags: @product @check_tor_leaks
0.000
Scenario Connecting to an SSH server on the Internet works and uses the default SocksPort
Steps
Given I monitor the network connections of SSH 0.000
And I have the SSH key pair for an SSH server 0.000
When I connect to an SSH server on the Internet 0.000
Then I have sucessfully logged into the SSH server 0.000
And I see that SSH is properly stream isolated 0.000
After features/support/hooks.rb:517 0.051
After features/support/hooks.rb:330 5.995 
SCENARIO FAILED: 'Connecting to an SSH server on the Internet works and uses the default SocksPort' (at time 04:59:08)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/04:59:08_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
1:24.872
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:24.872
Command 
Command failed (pid 52492 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/ssh.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Logging in via SSH
Tags: @product @check_tor_leaks
0.000
Scenario Connecting to an SSH server on the LAN
Steps
Given I have the SSH key pair for an SSH server 0.000
And an SSH server is running on the LAN 0.000
When I connect to an SSH server on the LAN 0.000
Then I am prompted to verify the SSH fingerprint for the SSH server 0.000
After features/support/hooks.rb:517 0.049
After features/support/hooks.rb:330 12.067 
SCENARIO FAILED: 'Connecting to an SSH server on the LAN' (at time 05:00:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:00:41_Connecting_to_an_SSH_server_on_the_LAN.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
41.291
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Before features/support/hooks.rb:509 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 41.291
Command 
Command failed (pid 52760 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/ssh.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Logging in via SSH
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature
Steps
Given I have the SSH key pair for an SFTP server 0.000
When I connect to an SFTP server on the Internet 0.000
Then I successfully connect to the SFTP server 0.000
After features/support/hooks.rb:517 0.034
After features/support/hooks.rb:330 10.527 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 05:01:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:01:33_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
27.947
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.055
Before features/support/hooks.rb:509 0.052
Steps
Given I have started Tails from DVD and logged in and the network is connected 27.947
Command 
Command failed (pid 52914 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/thunderbird.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
And I have not configured an email account yet 0.000
When I start Thunderbird 0.000
Then I am prompted to setup an email account 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
0.000
Scenario No add-ons are installed
Steps
Given I cancel setting up an email account 0.000
When I open Thunderbird's Add-ons Manager 0.000
And I open the Extensions tab 0.000
Then I see that no add-ons are enabled in Thunderbird 0.000
After features/support/hooks.rb:517 0.044
After features/support/hooks.rb:330 6.976 
SCENARIO FAILED: 'No add-ons are installed' (at time 05:02:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:11_No_add-ons_are_installed.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
29.046
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.046
Command 
Command failed (pid 53068 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/thunderbird.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
And I have not configured an email account yet 0.000
When I start Thunderbird 0.000
Then I am prompted to setup an email account 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
0.000
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 0.000
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:517 0.048
After features/support/hooks.rb:330 7.174 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 05:02:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:02:48_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
40.897
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 12.686
Then the Tor Connection Assistant reports that I am not connected to a local network 9.193
When I plug a Wi-Fi adapter 1.485
Then Tor Connection suggests me to connect to Wi-Fi 0.657
And I click on the Wi-Fi settings 1.485
And The Wi-Fi settings are displayed 15.389
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-control-center" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/tor.rb:1113:in `new'
./features/step_definitions/tor.rb:1113:in `/^The Wi-Fi settings are displayed$/'
features/tor_connection.feature:15:in `And The Wi-Fi settings are displayed'
After features/support/hooks.rb:330 8.334 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 05:04:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:11_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:11_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:11_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:11_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product @not_release_blocker
12.610
Scenario Bridges are not enabled in automatic mode when going back from hiding Tor
Steps
When the network is plugged 12.610
Command 
Command failed (pid 53495 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/tor_connection.feature:44:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I look at the hide mode but then I go back 0.000
And I choose to connect to Tor automatically 0.000
Then Tor Connection does not propose me to use Tor bridges 0.000
After features/support/hooks.rb:330 6.525 
SCENARIO FAILED: 'Bridges are not enabled in automatic mode when going back from hiding Tor' (at time 05:04:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:04:48_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
25.787
Scenario I can use a network with captive portal
Steps
Given the Tor network and default bridges are blocked 3.775
And the network is plugged 22.011
Command 
Command failed (pid 53647 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/tor_connection.feature:52:in `And the network is plugged'
And I make sure time sync before Tor connects indicates a captive portal 0.000
And the Tor Connection Assistant autostarts 0.000
When I choose to connect to Tor automatically 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant fails to connect to Tor 0.000
And the Tor Connection Assistant knows that it's not the time sync that failed 0.000
And the Tor Connection Assistant knows that there might be a captive portal 0.000
When I open the Unsafe Browser from Tor Connection 0.000
And I log-in to the Captive Portal 0.000
And I close the Unsafe Browser 0.000
And the Tor network and default bridges are unblocked 0.000
And I allow time sync before Tor connects to work again 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
After features/support/hooks.rb:330 11.445 
SCENARIO FAILED: 'I can use a network with captive portal' (at time 05:05:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:05:34_I_can_use_a_network_with_captive_portal.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
24.361
Scenario The firewall configuration is very restrictive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.053
Steps
Given I have started Tails from DVD and logged in and the network is connected 24.361
Command 
Command failed (pid 53801 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:9:in `Given I have started Tails from DVD and logged in and the network is connected'
Then the firewall's policy is to drop all IPv4 traffic 0.000
And the firewall is configured to only allow the arti, clearnet and debian-tor users to connect directly to the Internet over IPv4 0.000
And the firewall's NAT rules only redirect traffic for the Unsafe Browser, Tor's TransPort, and DNSPort 0.000
And the firewall is configured to block all external IPv6 traffic 0.000
After features/support/hooks.rb:330 6.570 
SCENARIO FAILED: 'The firewall configuration is very restrictive' (at time 05:06:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:10_The_firewall_configuration_is_very_restrictive.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
36.390
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 36.390
Command 
Command failed (pid 54056 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:16:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
When I successfully start the Unsafe Browser 0.000
And I open the Tails homepage in the Unsafe Browser 0.000
And the Tails homepage loads in the Unsafe Browser 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.738 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:06:53)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:06:53_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
29.744
Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.744
Command 
Command failed (pid 54209 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:24:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I disable Tails' firewall 0.000
When I do a TCP DNS lookup of "torproject.org" 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.542 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector' (at time 05:07:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:07:30_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
53.733
Scenario Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 53.733
Command 
Command failed (pid 54580 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:31:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I disable Tails' firewall 0.000
When I do a UDP DNS lookup of "torproject.org" 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.315 
SCENARIO FAILED: 'Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector' (at time 05:08:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:08:30_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
34.425
Scenario Anti test: Detecting ICMP leaks of ping with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.425
Command 
Command failed (pid 54732 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:38:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I disable Tails' firewall 0.000
When I send some ICMP pings 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.398 
SCENARIO FAILED: 'Anti test: Detecting ICMP leaks of ping with the firewall leak detector' (at time 05:09:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:09:11_Anti_test:_Detecting_ICMP_leaks_of_ping_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product @check_tor_leaks
53.957
Scenario The Tor enforcement is effective at blocking untorified TCP connection attempts
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:509 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 53.957
Command 
Command failed (pid 54985 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:46:in `Given I have started Tails from DVD and logged in and the network is connected'
When I open an untorified TCP connection to 1.2.3.4 on port 42 0.000
Then the untorified connection fails 0.000
And the untorified connection is logged as dropped by the firewall 0.000
After features/support/hooks.rb:517 0.033
After features/support/hooks.rb:330 6.669 
SCENARIO FAILED: 'The Tor enforcement is effective at blocking untorified TCP connection attempts' (at time 05:10:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:11_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product @check_tor_leaks
29.103
Scenario The Tor enforcement is effective at blocking untorified UDP connection attempts
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Before features/support/hooks.rb:509 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.103
Command 
Command failed (pid 55139 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:53:in `Given I have started Tails from DVD and logged in and the network is connected'
When I open an untorified UDP connection to 1.2.3.4 on port 42 0.000
Then the untorified connection fails 0.000
And the untorified connection is logged as dropped by the firewall 0.000
After features/support/hooks.rb:517 0.046
After features/support/hooks.rb:330 6.527 
SCENARIO FAILED: 'The Tor enforcement is effective at blocking untorified UDP connection attempts' (at time 05:10:47)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:10:47_The_Tor_enforcement_is_effective_at_blocking_untorified_UDP_connection_attempts.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product @check_tor_leaks
43.075
Scenario The Tor enforcement is effective at blocking untorified ICMP connection attempts
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 43.075
Command 
Command failed (pid 55290 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:60:in `Given I have started Tails from DVD and logged in and the network is connected'
When I open an untorified ICMP connection to 1.2.3.4 0.000
Then the untorified connection fails 0.000
And the untorified connection is logged as dropped by the firewall 0.000
After features/support/hooks.rb:517 0.034
After features/support/hooks.rb:330 10.539 
SCENARIO FAILED: 'The Tor enforcement is effective at blocking untorified ICMP connection attempts' (at time 05:11:37)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1750156726/007relay/diff-cache/1164
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:11:37_The_Tor_enforcement_is_effective_at_blocking_untorified_ICMP_connection_attempts.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
23.525
Scenario The system DNS is always set up to use Tor's DNSPort
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 12.144
And the system DNS is using the local DNS resolver 0.027
And the network is plugged 11.353
Command 
Command failed (pid 55441 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/tor_enforcement.feature:68:in `And the network is plugged'
And I successfully configure Tor 0.000
Then the system DNS is still using the local DNS resolver 0.000
After features/support/hooks.rb:330 6.844 
SCENARIO FAILED: 'The system DNS is always set up to use Tor's DNSPort' (at time 05:12:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:12:11_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
1:30.327
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.070
Before features/support/hooks.rb:509 0.039
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:30.327
Command 
Command failed (pid 55923 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario tails-security-check is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-security-check 0.000
And I re-run tails-security-check 0.000
Then I see that tails-security-check is properly stream isolated after 10 seconds 0.000
After features/support/hooks.rb:517 0.051
After features/support/hooks.rb:330 6.390 
SCENARIO FAILED: 'tails-security-check is using the Tails-specific SocksPort' (at time 05:13:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:13:48_tails-security-check_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
34.865
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.865
Command 
Command failed (pid 56077 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario htpdate is using the Tails-specific SocksPort
Steps
When I monitor the network connections of htpdate 0.000
And I re-run htpdate 0.000
Then I see that htpdate is properly stream isolated 0.000
After features/support/hooks.rb:517 0.042
After features/support/hooks.rb:330 6.235 
SCENARIO FAILED: 'htpdate is using the Tails-specific SocksPort' (at time 05:14:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:14:30_htpdate_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
34.224
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.224
Command 
Command failed (pid 56328 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.000
And I re-run tails-upgrade-frontend-wrapper 0.000
Then I see that tails-upgrade-frontend-wrapper is properly stream isolated 0.000
After features/support/hooks.rb:517 0.056
After features/support/hooks.rb:330 6.154 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 05:15:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:15:10_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
53.692
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 53.692
Command 
Command failed (pid 56581 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
0.000
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.000
And I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 6.274 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 05:16:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:10_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
36.585
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 36.585
Command 
Command failed (pid 56837 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
And a web server is running on the LAN 0.000
And I capture all network traffic 0.000
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
And I open a page on the LAN web server in the Tor Browser 0.000
Then the Tor Browser shows the "Unable to connect" error 0.000
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 6.706 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:16:53)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:16:53_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
27.090
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 27.090
Command 
Command failed (pid 56989 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:19:in `Given I have started Tails from DVD and logged in and the network is connected'
Then the live user's Downloads directory exists 0.000
And there is a GNOME bookmark for the Downloads directory 0.000
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then I can save the current page as "index.html" to the Downloads directory 0.000
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:517 0.044
After features/support/hooks.rb:330 7.024 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 05:17:27)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:17:27_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
42.013
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 42.013
Command 
Command failed (pid 57251 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:29:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
Then the Tor Browser loads the startup page 0.000
When I download some file in the Tor Browser to the Downloads directory 0.000
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 10.458 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 05:18:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:16_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
24.094
Scenario Playing an Ogg audio track
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.053
Before features/support/hooks.rb:509 0.047
Steps
Given I have started Tails from DVD and logged in and the network is connected 24.094
Command 
Command failed (pid 57403 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:37:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then I can listen to an Ogg audio track in Tor Browser 0.000
After features/support/hooks.rb:517 0.043
After features/support/hooks.rb:330 6.264 
SCENARIO FAILED: 'Playing an Ogg audio track' (at time 05:18:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:18:51_Playing_an_Ogg_audio_track.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
38.823
Scenario Watching a WebM video
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 38.823
Command 
Command failed (pid 57659 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:44:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then I can watch a WebM video in Tor Browser 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 10.166 
SCENARIO FAILED: 'Watching a WebM video' (at time 05:19:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:19:36_Watching_a_WebM_video.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
24.423
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Steps
Given I have started Tails from DVD and logged in and the network is connected 24.423
Command 
Command failed (pid 57812 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:50:in `Given I have started Tails from DVD and logged in and the network is connected'
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.000
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.000
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.000
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.000
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.000
And the file "/tmp/synaptic.html" exists 0.000
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.000
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 0.000
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 0.000
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 7.021 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 05:20:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:11_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
34.178
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.178
Command 
Command failed (pid 58061 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:74:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
Then the Tor Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 7.249 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 05:20:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:20:52_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
29.372
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.372
Command 
Command failed (pid 58226 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:80:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
When I open the address "https://example.com/" in the Tor Browser 0.000
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 0.000
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads the startup page 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:517 0.036
After features/support/hooks.rb:330 6.177 
SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 05:21:29)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:21:29_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
40.141
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 40.141
Command 
Command failed (pid 58489 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:91:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:330 9.056 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:22:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:15_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
26.032
Scenario WebRTC is disabled in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.107
Steps
Given I have started Tails from DVD and logged in and the network is connected 26.032
Command 
Command failed (pid 58641 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_browsing.feature:97:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
When I open the address "https://net.ipcalf.com/" in the Tor Browser 0.000
Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page 0.000
When I open the address "https://mozilla.github.io/webrtc-landing/pc_test.html" in the Tor Browser 0.000
Then Tor Browser displays a "RTCPeerConnection is missing!" heading on the "Simple RTCPeerConnection Video Test" page 0.000
After features/support/hooks.rb:330 6.351 
SCENARIO FAILED: 'WebRTC is disabled in Tor Browser' (at time 05:22:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:22:50_WebRTC_is_disabled_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
32.086
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.202
And the network is plugged 13.883
Command 
Command failed (pid 58836 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/torified_browsing.feature:107:in `And the network is plugged'
And I successfully configure Tor 0.000
And available upgrades have been checked 0.000
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 7.104 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 05:23:29)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:23:29_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:9.958
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD without network and logged in 1:9.958
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:91:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:97:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:74: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/torified_browsing.feature:127:in `Given I have started Tails from DVD without network and logged in'
features/torified_browsing.feature:120:in `Given I have started Tails from DVD without network and logged in'
Then the live user's Documents directory exists 0.000
And there is a GNOME bookmark for the Documents directory 0.000
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Documents GNOME bookmark 0.000
After features/support/hooks.rb:330 6.031 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 05:24:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:24:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:24:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:24:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:24:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Cloning a Git repository
35.342
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 35.342
Command 
Command failed (pid 61449 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_git.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Cloning a Git repository
Tags: @product @check_tor_leaks
0.000
Scenario Cloning a Git repository anonymously over HTTPS
Steps
When I clone the Git repository "https://github.com/intrigeri/Dist-Zilla-Plugin-LocaleMsgfmt.git" in GNOME Terminal 0.000
Then the Git repository "Dist-Zilla-Plugin-LocaleMsgfmt" has been cloned successfully 0.000
After features/support/hooks.rb:517 0.056
After features/support/hooks.rb:330 6.358 
SCENARIO FAILED: 'Cloning a Git repository anonymously over HTTPS' (at time 05:37:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:11_Cloning_a_Git_repository_anonymously_over_HTTPS.journal
After features/support/hooks.rb:100 0.000
Feature: Cloning a Git repository
37.009
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 37.009
Command 
Command failed (pid 61711 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_git.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Cloning a Git repository
Tags: @product @check_tor_leaks
0.000
Scenario Cloning git repository over SSH
Steps
Given I have the SSH key pair for a Git repository 0.000
When I clone the Git repository "ssh://gitolite3@lizard.tails.boum.org:3004/myprivatekeyispublic/testing.git" in GNOME Terminal 0.000
Then the Git repository "testing" has been cloned successfully 0.000
After features/support/hooks.rb:517 0.033
After features/support/hooks.rb:330 8.371 
SCENARIO FAILED: 'Cloning git repository over SSH' (at time 05:37:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:37:54_Cloning_git_repository_over_SSH.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
26.275
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.044
Before features/support/hooks.rb:509 0.034
Steps
Given I have started Tails from DVD and logged in and the network is connected 26.275
Command 
Command failed (pid 61864 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_misc.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
0.000
Scenario wget(1) should work for HTTPS and go through Tor
Steps
When I wget "https://example.com/" to stdout 0.000
Then the wget command is successful 0.000
And the wget standard output contains "Example Domain" 0.000
After features/support/hooks.rb:517 0.037
After features/support/hooks.rb:330 5.935 
SCENARIO FAILED: 'wget(1) should work for HTTPS and go through Tor' (at time 05:38:29)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:38:29_wget_1__should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
35.148
Background
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 and logged in and the network is connected 35.148
Command 
Command failed (pid 62130 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/torified_misc.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
0.000
Scenario curl should work for HTTPS and go through Tor
Steps
When I curl "https://example.com/" to stdout 0.000
Then the curl command is successful 0.000
And the curl standard output contains "Example Domain" 0.000
After features/support/hooks.rb:517 0.038
After features/support/hooks.rb:330 6.141 
SCENARIO FAILED: 'curl should work for HTTPS and go through Tor' (at time 05:39:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:39:10_curl_should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product @check_tor_leaks
50.525
Scenario Watching a WebM video over HTTPS
Steps
Given I have started Tails from DVD and logged in and the network is connected 50.525
Command 
Command failed (pid 62808 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/totem.feature:51:in `Given I have started Tails from DVD and logged in and the network is connected'
Then I can watch a WebM video over HTTPs 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 6.210 
SCENARIO FAILED: 'Watching a WebM video over HTTPS' (at time 05:41:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:41:48_Watching_a_WebM_video_over_HTTPS.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
1:46.517
Scenario The Unsafe Browser can be disabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.143
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 16.360
And I disable the Unsafe Browser 13.859
And I log in to a new session 35.472
And the network is plugged 40.824
Command 
Command failed (pid 63479 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/unsafe_browser.feature:11:in `And the network is plugged'
And all notifications have disappeared 0.000
When I try to start the Unsafe Browser 0.000
Then the Unsafe Browser complains that it is disabled 0.000
After features/support/hooks.rb:330 5.880 
SCENARIO FAILED: 'The Unsafe Browser can be disabled' (at time 05:44:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:44:49_The_Unsafe_Browser_can_be_disabled.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
35.890
Scenario The Unsafe Browser can access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 35.890
Command 
Command failed (pid 63742 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:17:in `Given I have started Tails from DVD and logged in and the network is connected'
And a web server is running on the LAN 0.000
When I successfully start the Unsafe Browser 0.000
And I open a page on the LAN web server in the Unsafe Browser 0.000
Then the Unsafe Browser displays the LAN web server hello message 0.000
After features/support/hooks.rb:330 6.514 
SCENARIO FAILED: 'The Unsafe Browser can access the LAN' (at time 05:45:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:45:31_The_Unsafe_Browser_can_access_the_LAN.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @doc
52.894
Scenario Starting the Unsafe Browser works as it should
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD and logged in and the network is connected 52.894
Command 
Command failed (pid 64000 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:25:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
Then the Unsafe Browser runs as the expected user 0.000
And the Unsafe Browser has a red theme 0.000
And the Unsafe Browser shows a warning as its start page 0.000
And the Unsafe Browser has no add-ons installed 0.000
And the Unsafe Browser has no bookmarks 0.000
And the Unsafe Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.348 
SCENARIO FAILED: 'Starting the Unsafe Browser works as it should' (at time 05:46:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:46:30_Starting_the_Unsafe_Browser_works_as_it_should.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
48.604
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.084
Steps
Given I have started Tails from DVD and logged in and the network is connected 48.604
Command 
Command failed (pid 64153 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:35:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
When I open the Tails homepage in the Unsafe Browser 0.000
Then the Tails homepage loads in the Unsafe Browser 0.000
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 7.410 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 05:47:26)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:47:26_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
41.307
Scenario Closing the Unsafe Browser shows a stop notification and properly tears down the chroot
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 41.307
Command 
Command failed (pid 64418 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:43:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
And I close the Unsafe Browser 0.000
Then I see the "Shutting down the Unsafe Browser..." notification after at most 60 seconds 0.000
And the Unsafe Browser chroot is torn down 0.000
After features/support/hooks.rb:330 10.862 
SCENARIO FAILED: 'Closing the Unsafe Browser shows a stop notification and properly tears down the chroot' (at time 05:48:14)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:14_Closing_the_Unsafe_Browser_shows_a_stop_notification_and_properly_tears_down_the_chroot.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
25.273
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Steps
Given I have started Tails from DVD and logged in and the network is connected 25.273
Command 
Command failed (pid 64571 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:51:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 0.000
And I try to start the Unsafe Browser 0.000
Then I see a warning about another instance already running 0.000
After features/support/hooks.rb:330 6.388 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 05:48:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:48:51_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
41.849
Scenario The Unsafe Browser is not allowed to use a local proxy
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 41.849
Command 
Command failed (pid 64831 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:62:in `Given I have started Tails from DVD and logged in and the network is connected'
When I configure the Unsafe Browser to use a local proxy 0.000
And I successfully start the Unsafe Browser 0.000
And I open the Tails homepage in the Unsafe Browser 0.000
Then the Unsafe Browser shows the "The proxy server is refusing connections" error 0.000
After features/support/hooks.rb:330 10.822 
SCENARIO FAILED: 'The Unsafe Browser is not allowed to use a local proxy' (at time 05:49:40)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:49:40_The_Unsafe_Browser_is_not_allowed_to_use_a_local_proxy.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker @check_tor_leaks
23.194
Scenario The Unsafe Browser only makes user-initiated non-Torified connections
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Before features/support/hooks.rb:509 0.019
Steps
Given I have started Tails from DVD and logged in and the network is connected 23.194
Command 
Command failed (pid 64982 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:70:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I configure the Unsafe Browser to check for updates more frequently 0.000
But checking for updates is disabled in the Unsafe Browser's configuration 0.000
When I successfully start the Unsafe Browser 0.000
And I wait 120 seconds 0.000
Then the Unsafe Browser has not sent packets out to the Internet 0.000
After features/support/hooks.rb:517 0.045
After features/support/hooks.rb:330 6.835 
SCENARIO FAILED: 'The Unsafe Browser only makes user-initiated non-Torified connections' (at time 05:50:13)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:13_The_Unsafe_Browser_only_makes_user-initiated_non-Torified_connections.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
29.119
Scenario The Unsafe Browser cannot be started when I am offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.119
Command 
Command failed (pid 65139 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:80:in `Given I have started Tails from DVD and logged in and the network is connected'
And the network is unplugged 0.000
# NetworkManager apparently needs some time to notice that the connection is now off
And I wait 10 seconds 0.000
When I try to start the Unsafe Browser 0.000
Then I am told I cannot start the Unsafe Browser when I am offline 0.000
After features/support/hooks.rb:330 6.024 
SCENARIO FAILED: 'The Unsafe Browser cannot be started when I am offline' (at time 05:50:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/05:50:49_The_Unsafe_Browser_cannot_be_started_when_I_am_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
38.380
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 26.712
And I unlock and mount this VeraCrypt file container with GNOME Disks 11.667
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

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