Project Number Date
test_Tails_ISO_feature-arti 97 24 Jun 2025, 21:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
5:0.716
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.980
When the network is plugged 0.073
And the Tor Connection Assistant autostarts 4.468
And I configure some normal bridges in the Tor Connection Assistant 15.762
And I wait until Tor is ready 4:31.432
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:18:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.044
After features/support/hooks.rb:330 5.472 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:17:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:17:19_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
5:1.243
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.002
Steps
Given I have started Tails from DVD without network and logged in 8.198
When I bump the system time with "+1 day" 0.312
And I capture all network traffic 0.006
And the network is plugged 0.245
And the Tor Connection Assistant autostarts 5.135
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.286
And I wait until Tor is ready 4:32.057
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:28:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:517 0.038
After features/support/hooks.rb:330 5.580 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:22:26)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:22:26_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/97/artifact/build-artifacts/00:22:26_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/97/artifact/build-artifacts/00:22:26_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/97/artifact/build-artifacts/00:22:26_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:22:26_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/97/artifact/build-artifacts/00:22:26_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.054
Feature: Time syncing
Tags: @product @check_tor_leaks
5:28.535
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.828
When I bump the system time with "+8 hours +15 minutes" 0.380
And all notifications have disappeared 4.689
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.109
And the network is plugged 0.100
And the Tor Connection Assistant autostarts 4.034
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.306
And I click "Connect to Tor" 1.321
And the Tor Connection Assistant fails to connect to Tor 15.953
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 15.049
Then the system clock is less than 20 minutes incorrect 0.331
When I click "Connect to Tor" 1.220
Then I wait until Tor is ready 4:30.206
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:77:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.084
After features/support/hooks.rb:330 6.014 
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:32:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:32:55_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/97/artifact/build-artifacts/00:32:55_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/97/artifact/build-artifacts/00:32:55_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/97/artifact/build-artifacts/00:32:55_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/97/artifact/build-artifacts/00:32:55_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/97/artifact/build-artifacts/00:32:55_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.029
Feature: Time syncing
Tags: @product @check_tor_leaks
5:23.089
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 8.581
When I bump the system time with "+8 hours +15 minutes" 0.262
And all notifications have disappeared 4.332
And I capture all network traffic 0.042
And the network is plugged 0.226
And the Tor Connection Assistant autostarts 4.732
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.733
And I click "Connect to Tor" 1.159
Then the Tor Connection Assistant reports that it failed to connect 11.745
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 15.144
Then the system clock is less than 20 minutes incorrect 0.319
# "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.391
When I click "Connect to Tor" 1.158
Then I wait until Tor is ready 4:30.258
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:99:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:517 0.032
After features/support/hooks.rb:330 5.577 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:38:24)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:38:24_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:38:24_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/97/artifact/build-artifacts/00:38:24_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:38:24_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:38:24_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/97/artifact/build-artifacts/00:38:24_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.069
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:44.310
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 13.225
Then I wait until Tor is ready 4:31.085
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:15:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.253 
SCENARIO FAILED: 'Using normal bridges' (at time 00:43:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:43:56_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:45.132
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 14.028
Then I wait until Tor is ready 4:31.104
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:22:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.769 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:49:02)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:49:02_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:7.220
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 33.695
Then I wait until Tor is ready 4:33.525
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:29:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 7.169 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:54:32)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:54:32_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:54:32_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/97/artifact/build-artifacts/00:54:32_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:54:32_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:54:32_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/00:54:32_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:35.085
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 6.355
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 32.590
Then the Tor Connection Assistant reports that it failed to connect 0.154
And tca.conf is empty 0.294
Given I scan a QR code from the error page in Tor Connection Assistant 23.218
And I retry connecting to Tor 1.347
Then I wait until Tor is ready 4:31.123
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:41:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.084 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 01:00:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:00:28_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:00:28_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/97/artifact/build-artifacts/01:00:28_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:00:28_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:00:28_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:00:28_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:51.480
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 20.107
Then I wait until Tor is ready 4:31.373
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:49:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.503 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:05:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:05:41_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.058
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.009
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 1.691
When I configure a direct connection in the Tor Connection Assistant 21.425
Then I wait until Tor is ready 4:30.892
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:59:in `Then I wait until Tor is ready'
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.939 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:10:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:10:59_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.030
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:4.040
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 6.423
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 24.003
Then the Tor Connection Assistant reports that it failed to connect 0.170
Given the Tor network and default bridges are unblocked 1.943
When I click "Connect to Tor" 1.279
Then I wait until Tor is ready 4:30.220
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:108:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.662 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:22:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:22:22_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/97/artifact/build-artifacts/01:22:22_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/97/artifact/build-artifacts/01:22:22_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/97/artifact/build-artifacts/01:22:22_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/97/artifact/build-artifacts/01:22:22_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/97/artifact/build-artifacts/01:22:22_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.048
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:16.510
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.460
And I prepare Tails for memory erasure tests 3.009
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 48.186
Then I find very few patterns in the guest's memory 2.779 
Pattern coverage: 0.000% (0 MiB out of 891 MiB reference memory)
# write cache
When I fill the USB drive with a known pattern 2.619
Then patterns cover at least 99% of the test FS size in the guest's memory 10.455
92.510% 
92.510% of the test FS size (91.490234375 MiB) has the pattern, but more than 99.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/erase_memory.feature:54:in `Then patterns cover at least 99% of the test FS size in the guest's memory'
Output 1 
Pattern coverage: 92.510% (84 MiB out of 91 MiB reference memory)
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
After features/support/hooks.rb:330 5.832 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 01:26:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:26:21_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:26:21_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:26:21_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:26:21_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:22.149
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 5.606 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:55:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:55:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:55:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:55:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:55:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:13.364
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:13.364
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I temporarily create a 7200 MiB disk named "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.906 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 01:57:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:57:02_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:57:02_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:57:02_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/01:57:02_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
4:28.669
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.006
Before features/support/hooks.rb:509 0.005
Steps
Given a computer 0.194
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:28.474
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:664:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:618:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:311: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.169
After features/support/hooks.rb:330 5.844 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:46:22)
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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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/97/artifact/build-artifacts/02:46:22_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.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
8:25.495
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.004
Steps
Given a computer 0.185
And I start Tails from USB drive "__internal" with network unplugged 1:43.257
And I enable persistence 22.221
And I remove the "cowsay" deb files from the APT cache 0.526
# 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 1.730
And I log in to a new session 1:16.136
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.436
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/common_steps.rb:610:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
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.053
After features/support/hooks.rb:330 10.798 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:54:55)
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/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/02:54:55_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/97/artifact/build-artifacts/02:54:55_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.035
Feature: Backing up the persistent storage
Tags: @product
1:23.067
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.509
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.067
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/backup.feature:8:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 0.000
And I clone USB drive "__internal" to a temporary USB drive "backup" 0.000
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 0.000
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 6.811 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:46:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:46:01_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:46:01_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:46:01_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:46:01_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.000
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
20.644
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.076
Steps
Given I have started Tails from DVD without network and logged in 9.890
When I start "Tails Documentation" via GNOME Activities Overview 10.753
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:1152:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
features/documentation.feature:6:in `When I start "Tails Documentation" via GNOME Activities Overview'
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 5.507 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 03:50:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:50:25_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:50:25_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:50:25_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:50:25_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
1:55.626
Scenario The Tails documentation launcher works when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 57.339
When I start "Tails Documentation" via GNOME Activities Overview 12.389
Then the Tor Browser has started 45.898
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:13:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 6.286 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 03:52:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:52:26_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/97/artifact/build-artifacts/03:52:26_The_Tails_documentation_launcher_works_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:52:26_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:52:26_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:100 0.000
Feature: Electrum Bitcoin client
Tags: @product @check_tor_leaks
32.055
Scenario I am warned if Electrum is not persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.005
Steps
Given I have started Tails from DVD without network and logged in 20.272
When I start Electrum through the GNOME menu 11.782
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:1152:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
./features/step_definitions/electrum.rb:14:in `/^I start Electrum through the GNOME menu$/'
features/electrum.feature:9:in `When I start Electrum through the GNOME menu'
But the "electrum" tps feature is not enabled 0.000
And I see a warning that Electrum is not persistent 0.000
After features/support/hooks.rb:517 0.050
After features/support/hooks.rb:330 5.568 
SCENARIO FAILED: 'I am warned if Electrum is not persistent' (at time 03:53:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:53:05_I_am_warned_if_Electrum_is_not_persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:53:05_I_am_warned_if_Electrum_is_not_persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:53:05_I_am_warned_if_Electrum_is_not_persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:53:05_I_am_warned_if_Electrum_is_not_persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product
1:12.277
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.277
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.000
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000
Then I see "CupsTestPage.png" after at most 40 seconds 0.000
And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000
After features/support/hooks.rb:330 6.862 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 03:57:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:57:02_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:57:02_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:57:02_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/03:57:02_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:33.556
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.010
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 16.249
When I log in to a new session in Spanish (es) 42.167
Then the keyboard layout is set to "es" 0.326
When the network is plugged 0.169
And Tor is ready 21.237
Then I successfully start the Unsafe Browser 32.910
And I kill the Unsafe Browser 6.805
When I enable the screen keyboard 0.164
Then the screen keyboard works in Tor Browser 33.526
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:56:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
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.957 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 05:17:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:17:06_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/97/artifact/build-artifacts/05:17:06_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:17:06_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:17:06_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
7.477
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:534 0.000
Steps
Given I have the build manifest for the image under test 0.001
Then all packages listed in the build manifest are up-to-date 7.475
Command 
Command failed (pid 47050 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/tmp/tails-amd64-feature_arti@5d1c7305de+stable@9c8c625ee5-20250624T1211Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/tmp/tails-amd64-feature_arti@5d1c7305de+stable@9c8c625ee5-20250624T1211Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - ublock-origin (1.62.0+dfsg-1) to Debian trixie (1.62.0+dfsg-2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:325:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/support/helpers/misc_helpers.rb:325:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:541 0.000
After features/support/hooks.rb:100 0.000
Feature: Networking
Tags: @product
1:54.836
Scenario No initial network
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails from DVD without network and logged in 28.242
And I wait between 30 and 60 seconds 47.089 
Slept for 47 seconds
Then the Tor Status icon tells me that Tor is not usable 0.852
When the network is plugged 0.082
Then I successfully configure Tor 27.264
And the Tor Status icon tells me that Tor is usable 11.305
cannot 
cannot find TorStatusUsable.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/checks.rb:319:in `/^the Tor Status icon tells me that Tor is( not)? usable$/'
features/networking.feature:10:in `And the Tor Status icon tells me that Tor is usable'
And all notifications have disappeared 0.000
And the time has synced 0.000
After features/support/hooks.rb:330 5.517 
SCENARIO FAILED: 'No initial network' (at time 05:33:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:33:45_No_initial_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:33:45_No_initial_network.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:33:45_No_initial_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:33:45_No_initial_network.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
37.089
Scenario Booting Tails from a USB drive with a disabled 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 and stopped at Tails Greeter's login screen 22.462
When I log in to a new session without activating the Persistent Storage 14.627
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:530:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:14:in `When I log in to a new session without activating the Persistent Storage'
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:330 7.224 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 05:43:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:43:45_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:43:45_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:43:45_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:43:45_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.668
Scenario Creating a Persistent Storage when system is low on memory
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:29.668
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\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:31:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And the system is very low on memory 0.000
When I create a file in the Persistent directory 0.000
When I try to create a persistent partition 0.000
Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.000
When I close the Persistent Storage app 0.000
And I free up some memory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
After features/support/hooks.rb:330 5.690 
SCENARIO FAILED: 'Creating a Persistent Storage when system is low on memory' (at time 05:51:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:51:43_Creating_a_Persistent_Storage_when_system_is_low_on_memory.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:51:43_Creating_a_Persistent_Storage_when_system_is_low_on_memory.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:51:43_Creating_a_Persistent_Storage_when_system_is_low_on_memory.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/05:51:43_Creating_a_Persistent_Storage_when_system_is_low_on_memory.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:14.382
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.382
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:330 6.572 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 06:00:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:00:01_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:00:01_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:00:01_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:00:01_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:17.118
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.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.118
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
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 6.091 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 06:01:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:01:24_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/97/artifact/build-artifacts/06:01:24_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:01:24_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:01:24_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:12.457
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.457
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:117:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 7.491 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 06:20:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:20:01_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:20:01_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:20:01_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:20:01_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:16.343
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.343
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 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 and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 6.069 
SCENARIO FAILED: 'Dotfiles persistence' (at time 06:23:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:23:42_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:23:42_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:23:42_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:23:42_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.878
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 27.234
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.859
When I try to enable persistence 1.779
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.004
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:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 21.212 
SCENARIO FAILED: 'Feature activation fails' (at time 06:25:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:25:23_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:25:23_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:25:23_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:31.594
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 19.449
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 11.685
When I try to enable persistence 0.439
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.020
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 18.124 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 06:39:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:39:37_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:39:37_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:39:37_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:55.752
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 48.697
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 3.316
When I try to enable persistence 3.732
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.006
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 16.659 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 06:41:46)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:41:46_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:41:46_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:41:46_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
7:21.770
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:13.705
And I create a persistent partition with the default settings 54.947
Then the "TorConfiguration" tps feature is not enabled 2.985
When the network is plugged 0.069
And the Tor Connection Assistant autostarts 16.792
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 22.561
And I wait until Tor is ready 4:30.707
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.283 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 06:54:24)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:54:24_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
2:6.396
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 42.283
And I create a persistent partition with the default settings 56.157
Then the "TorConfiguration" tps feature is not enabled 3.378
When the network is plugged 0.092
And the Tor Connection Assistant autostarts 15.119
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.364
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 7.040 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 06:56:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:56:42_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:56:42_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:56:42_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/06:56:42_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:32.353
Scenario The live user is setup correctly
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 1:32.353
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/sane_defaults.feature:5:in `Given I have started Tails from DVD without network and logged in'
Then the live user has been setup by live-boot 0.000
And the live user is a member of only its own group and "cdrom dialout floppy video plugdev netdev scanner lp lpadmin users" 0.000
And the live user owns its home directory which has strict permissions 0.000
After features/support/hooks.rb:330 6.139 
SCENARIO FAILED: 'The live user is setup correctly' (at time 07:04:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:04:25_The_live_user_is_setup_correctly.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:04:25_The_live_user_is_setup_correctly.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:04:25_The_live_user_is_setup_correctly.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:04:25_The_live_user_is_setup_correctly.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
1:30.100
Scenario No unexpected network services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:30.100
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\ 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 6.090 
SCENARIO FAILED: 'No unexpected network services' (at time 07:06:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:06:02_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:06:02_No_unexpected_network_services.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:06:02_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:06:02_No_unexpected_network_services.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:17.820
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.820
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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 6.536 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 07:10:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:10:23_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:10:23_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:10:23_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:10:23_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
1:15.757
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:15.757
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\ 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 7.237 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 07:11:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:11:45_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/97/artifact/build-artifacts/07:11:45_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:11:45_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:11:45_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
1:34.348
Scenario I can reboot Tails via the system menu
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 1:34.348
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\ 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.357 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 07:13:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:13:27_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/97/artifact/build-artifacts/07:13:27_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:13:27_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:13:27_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
1:31.555
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:509 0.012
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:31.555
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\ 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 successfully 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.036
After features/support/hooks.rb:330 6.991 
SCENARIO FAILED: 'Connecting to an SSH server on the Internet works and uses the default SocksPort' (at time 07:15:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:15:05_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/97/artifact/build-artifacts/07:15:05_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:15:05_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/97/artifact/build-artifacts/07:15:05_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:28.056
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Before features/support/hooks.rb:509 0.020
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:28.056
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\ 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.045
After features/support/hooks.rb:330 7.240 
SCENARIO FAILED: 'Connecting to an SSH server on the LAN' (at time 07:16:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:16: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/97/artifact/build-artifacts/07:16:41_Connecting_to_an_SSH_server_on_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:16:41_Connecting_to_an_SSH_server_on_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:16:41_Connecting_to_an_SSH_server_on_the_LAN.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:25.533
Scenario The Tor Browser cannot access the LAN
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.976
And a web server is running on the LAN 1.784
And I capture all network traffic 0.030
When I start the Tor Browser 35.853
And the Tor Browser loads the startup page 3.301
And I open a page on the LAN web server in the Tor Browser 14.587
Then the Tor Browser shows the "Unable to connect" error 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:334:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 12.860 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 07:34:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:34:54_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:34:54_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:34:54_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.049
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
55.074
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:509 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.871
When I start the Tor Browser 36.202
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:30:in `When I start the Tor Browser'
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.051
After features/support/hooks.rb:330 5.845 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 07:37:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:37:23_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:37:23_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:37:23_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:37:23_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
1:36.415
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.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.723
When I start the Tor Browser 36.637
And the Tor Browser loads the startup page 1.201
Then Tor Browser's circuit view is working 40.852
The 
The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Tor Circuit" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:435:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:94:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 7.459 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 07:47:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:47:09_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/97/artifact/build-artifacts/07:47:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:47:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/97/artifact/build-artifacts/07:47:09_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000