Project Number Date
test_Tails_ISO_improve-cmd-logging 3 17 Jul 2025, 16:58

Failures Overview

The following summary displays scenarios that failed.

Feature: Root access control enforcement
Tags: @product
5:11.960
Scenario I can perform administrative tasks if I have set up an administration password in the Welcome Screen
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in with an administration password 5:11.960
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in\ with\ an\ administration\ password$/'
features/root_access_control.feature:7:in `Given I have started Tails from DVD without network and logged in with an administration password'
And running a command as root with pkexec requires PolicyKit administrator privileges 0.000
Then I can run a command as root with sudo 0.000
Then I can run a command as root with pkexec 0.000
After features/support/hooks.rb:330 6.418 
SCENARIO FAILED: 'I can perform administrative tasks if I have set up an administration password in the Welcome Screen' (at time 00:17:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:17:18_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:17:18_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:17:18_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:17:18_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal
After features/support/hooks.rb:100 0.017
Feature: Time syncing
Tags: @product @check_tor_leaks
32.922
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 20.718
When the network is plugged 12.203
Command 
Command failed (pid 5857 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 7.669 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:38.581
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 1:22.583
When the network is plugged 15.997
Command 
Command failed (pid 6352 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.036
After features/support/hooks.rb:330 15.199 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:23:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:18.465
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.005
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 48.698
When I bump the system time with "+1 day" 5.502
And I capture all network traffic 0.110
And the network is plugged 24.154
Command 
Command failed (pid 6732 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:25:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:517 0.041
After features/support/hooks.rb:330 6.635 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:24:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_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_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.048
Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
1:12.875
Scenario Anti-test: Changes to the hardware clock are kept when rebooting
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Before features/support/hooks.rb:509 0.013
Steps
Given I have started Tails from DVD without network and logged in 1:12.875
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/time_syncing.feature:42:in `Given I have started Tails from DVD without network and logged in'
When I bump the hardware clock's time with "-15 days" 0.000
And I warm reboot the computer 0.000
And the computer reboots Tails 0.000
Then the hardware clock is still off by "-15 days" 0.000
After features/support/hooks.rb:517 0.042
After features/support/hooks.rb:330 8.201 
SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:28:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:11.733
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:11.733
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/time_syncing.feature:56:in `Given I have started Tails from DVD without network and logged in'
And I make sure time sync before Tor connects times out 0.000
When the network is plugged 0.000
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.036
After features/support/hooks.rb:330 6.950 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:32:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:36.073
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.004
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:8.851
When I bump the system time with "+8 hours +15 minutes" 2.667
And all notifications have disappeared 9.284
And I capture all network traffic 0.018
And I make sure time sync before Tor connects fails 0.257
And the network is plugged 14.994
Command 
Command failed (pid 8895 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:68:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 0.000
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.040
After features/support/hooks.rb:330 6.399 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:33:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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.054
Feature: Time syncing
Tags: @product @check_tor_leaks
48.035
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.010
Before features/support/hooks.rb:509 0.013
Steps
Given I have started Tails from DVD without network and logged in 21.805
When I bump the system time with "+8 hours +15 minutes" 0.228
And all notifications have disappeared 13.549
And I capture all network traffic 0.003
And the network is plugged 12.448
Command 
Command failed (pid 9065 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:87:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:517 0.039
After features/support/hooks.rb:330 8.515 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:34:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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.034
Feature: Time syncing
Tags: @product @check_tor_leaks
1:54.165
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 56.073
And I make sure time sync before Tor connects uses a fake connectivity check service 1.483
And the network is plugged 56.609
Command 
Command failed (pid 9454 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:108:in `And the network is plugged'
And Tor is ready 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
When I make NetworkManager perform a connectivity check 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
And the HTTP requests received by the fake connectivity check service are identical 0.000
After features/support/hooks.rb:517 0.043
After features/support/hooks.rb:330 6.021 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:36:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.000
Feature: Using Tor bridges and pluggable transports
39.668
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 26.592
And I capture all network traffic 0.254
When the network is plugged 12.822
Command 
Command failed (pid 9715 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 12.569 
SCENARIO FAILED: 'Using normal bridges' (at time 00:37:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:37:42_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.055
Feature: Using Tor bridges and pluggable transports
44.302
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Steps
Given I have started Tails from DVD without network and logged in 14.326
And I capture all network traffic 0.269
When the network is plugged 29.706
Command 
Command failed (pid 9868 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 7.028 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:38:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:38:39_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.068
Feature: Using Tor bridges and pluggable transports
32.813
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 20.212
And I capture all network traffic 0.005
When the network is plugged 12.596
Command 
Command failed (pid 10031 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 6.348 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:39:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:19_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
32.324
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD without network and logged in 21.194
And I capture all network traffic 0.004
When the network is plugged 11.126
Command 
Command failed (pid 10200 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given I scan a QR code from the error page in Tor Connection Assistant 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.531 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:39:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:39:58_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
35.748
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD without network and logged in 24.436
And I capture all network traffic 0.107
When the network is plugged 11.204
Command 
Command failed (pid 10451 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
0.000
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.484 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:40:40)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:40:40_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.047
Feature: Using Tor bridges and pluggable transports
31.300
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 19.825
And I capture all network traffic 0.002
When the network is plugged 11.471
Command 
Command failed (pid 10606 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 0.000
When I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.343 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:41:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_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_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_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_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_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_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_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_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_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_improve-cmd-logging/3/artifact/build-artifacts/00:41:18_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.028
Feature: Using Tor bridges and pluggable transports
56.595
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 44.698
And I capture all network traffic 0.016
When the network is plugged 11.880
Command 
Command failed (pid 10968 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given the Tor network and default bridges are unblocked 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 9.261 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:42:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:42:21_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
50.868
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.056
Steps
Given I have started Tails from DVD without network and logged in 37.395
And I capture all network traffic 0.203
When the network is plugged 13.268
Command 
Command failed (pid 11301 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Normal bridges are not allowed in "Hide" mode
Steps
When I try to configure some normal bridges in the Tor Connection Assistant in hide mode 0.000
Then the Tor Connection Assistant complains that normal bridges are not allowed 0.000
And I cannot click the "Connect to Tor" button 0.000
After features/support/hooks.rb:330 7.878 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:43:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:43:21_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:100 0.057
Feature: Using Tor bridges and pluggable transports
32.875
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Steps
Given I have started Tails from DVD without network and logged in 18.740
And I capture all network traffic 0.223
When the network is plugged 13.912
Command 
Command failed (pid 11454 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
When I disconnect the network through GNOME 0.000
And I connect the network through GNOME 0.000
Then the Tor Connection Assistant autostarts 0.000
And the Tor Connection Assistant connects to Tor 0.000
And I wait until Tor is ready 0.000
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 10.514 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:44:03)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.035
Feature: Using Tor bridges and pluggable transports
30.440
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 16.996
And I capture all network traffic 0.134
When the network is plugged 13.309
Command 
Command failed (pid 11611 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Reconnecting from an unblocked network to a blocked network displays an error
Steps
Given I configure a direct connection in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
And I disconnect the network through GNOME 0.000
And the Tor network and default bridges are blocked 0.000
When I connect the network through GNOME 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
After features/support/hooks.rb:330 14.176 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:44:43)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:44:43_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
25.284
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 11.221
And I capture all network traffic 0.065
When the network is plugged 13.997
Command 
Command failed (pid 11761 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
Given the Tor network and default bridges are unblocked 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 11.643 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:45:23)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1752742957/003auth/diff-cache/1250
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_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_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_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_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:45:23_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.037
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:57.613
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.003
Steps
Given I have started Tails from DVD without network and logged in 33.399
And I prepare Tails for memory erasure tests 3.871
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 1:0.405
Then I find very few patterns in the guest's memory 4.077 
Pattern coverage: 0.000% (0 MiB out of 892 MiB reference memory)
# write cache
When I fill the USB drive with a known pattern 2.617
Then patterns cover at least 99% of the test FS size in the guest's memory 13.241
97.493% 
97.493% 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: 97.493% (89 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.727 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:52:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:52:39_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_improve-cmd-logging/3/artifact/build-artifacts/00:52:39_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:52:39_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:52:39_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:14.272
Scenario Erasure of the overlayfs read-write branch on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 1:14.272
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/erase_memory.feature:65:in `Given I have started Tails from DVD without network and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the root filesystem 0.000
# ensure the pattern is in memory due to tmpfs, not to disk cache
And I drop all kernel caches 0.000
Then patterns cover at least 128 MiB in the guest's memory 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 6.283 
SCENARIO FAILED: 'Erasure of the overlayfs read-write branch on shutdown' (at time 00:53:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:53:59_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:53:59_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:53:59_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:53:59_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
5:28.193
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5:28.193
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 10.042 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:59:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:59:36_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:59:36_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:59:36_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:59:36_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.037
Feature: Installing Tails to a USB drive
Tags: @product @not_release_blocker
1:34.940
Scenario Try installing Tails to a too small USB drive with GPT and a FAT partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails from DVD without network and logged in 1:34.940
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/usb_install.feature:8:in `Given I have started Tails from DVD without network and logged in'
And I temporarily create a 4 GiB disk named "gptfat" 0.000
And I create a gpt partition with a vfat filesystem on disk "gptfat" 0.000
And I plug USB drive "gptfat" 0.000
When I start Tails Installer 0.000
Then I am told by Tails Installer that the destination device "is too small" 0.000
After features/support/hooks.rb:330 6.376 
SCENARIO FAILED: 'Try installing Tails to a too small USB drive with GPT and a FAT partition' (at time 01:01:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:01:20_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:01:20_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:01:20_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:01:20_Try_installing_Tails_to_a_too_small_USB_drive_with_GPT_and_a_FAT_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
53.925
Scenario Detecting when a target USB drive is inserted or removed
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 27.127
And I temporarily create a 7200 MiB disk named "temp" 1.491
And I start Tails Installer 25.306
cannot 
cannot find TailsClonerWindow.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/usb.rb:156:in `/^I start Tails Installer$/'
features/usb_install.feature:18:in `And I start Tails Installer'
But a suitable USB device is not found 0.000
When I plug USB drive "temp" 0.000
Then the "temp" USB drive is selected 0.000
When I unplug USB drive "temp" 0.000
Then a suitable USB device is not found 0.000
After features/support/hooks.rb:330 6.564 
SCENARIO FAILED: 'Detecting when a target USB drive is inserted or removed' (at time 01:02:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:02:21_Detecting_when_a_target_USB_drive_is_inserted_or_removed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:02:21_Detecting_when_a_target_USB_drive_is_inserted_or_removed.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:02:21_Detecting_when_a_target_USB_drive_is_inserted_or_removed.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:02:21_Detecting_when_a_target_USB_drive_is_inserted_or_removed.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
5:9.441
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.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5:9.441
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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.854 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:18:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:18:17_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_improve-cmd-logging/3/artifact/build-artifacts/01:18:17_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_improve-cmd-logging/3/artifact/build-artifacts/01:18:17_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_improve-cmd-logging/3/artifact/build-artifacts/01:18:17_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.045
Feature: Installing Tails to a USB drive
Tags: @product
1:16.974
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.044
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.974
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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 6.129 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 01:19:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:19:40_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_improve-cmd-logging/3/artifact/build-artifacts/01:19:40_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_improve-cmd-logging/3/artifact/build-artifacts/01:19:40_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_improve-cmd-logging/3/artifact/build-artifacts/01:19:40_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: Installing Tails to a USB drive
Tags: @product
24:50.460
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24:50.460
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I have started Tails from DVD without network and logged in 0.000
And I clone USB drive "__internal" to a temporary USB drive "install" 0.000
And I plug USB drive "install" 0.000
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.366 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 01:44:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:44:36_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:44:36_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:44:36_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/01:44:36_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:1.868
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Before features/support/hooks.rb:509 0.049
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 4:1.868
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:312:in `/^I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login$/'
features/additional_software_packages.feature:28:in `Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login'
And I update APT using apt 0.000
And I install "popularity-contest" using apt 0.000
Then I am proposed to add the "popularity-contest" package to my Additional Software 0.000
When I create a persistent storage and activate the Additional Software feature 0.000
Then Additional Software is correctly configured for package "popularity-contest" 0.000
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 7.837 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 02:01:03)
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_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:01:03_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:15.286
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Before features/support/hooks.rb:509 0.014
Steps
Given a computer 0.887
And I start Tails from USB drive "__internal" and I login with an administration password 3:55.313
And I update APT using apt 26.856
When I install "makepp" using apt 44.287
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 1:7.941
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/additional_software_packages.rb:157:in `/^the Additional Software dpkg hook has been run for package "([^"]*)" and notices the persistence is locked$/'
features/additional_software_packages.feature:49:in `Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked'
And the package "makepp" is installed 0.000
After features/support/hooks.rb:517 0.043
After features/support/hooks.rb:330 13.180 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:07:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:07:28_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.021
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:9.705
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.010
Steps
Given a computer 0.290
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:9.415
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:517 0.154
After features/support/hooks.rb:330 9.116 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:09: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_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:09:55_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
2:3.198
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.002
Before features/support/hooks.rb:509 0.003
Steps
Given a computer 0.238
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:2.960
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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.033
After features/support/hooks.rb:330 13.660 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:12:07)
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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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_improve-cmd-logging/3/artifact/build-artifacts/02:12:07_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.010
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:0.922
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.006
Before features/support/hooks.rb:509 0.003
Steps
Given a computer 0.264
And I start Tails from USB drive "__internal" with network unplugged 1:40.741
And I enable persistence 19.916
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:517 0.046
After features/support/hooks.rb:330 5.857 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:14:19)
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_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_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_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_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_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_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_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_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_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/02:14:19_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.014
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:22.682
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.682
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 7.171 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:01:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
2:13.742
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.042
# 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 17.688
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.996
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:28.015
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/backup.feature:12:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 7.656 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:15:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:15:55_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_improve-cmd-logging/3/artifact/build-artifacts/03:15:55_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:15:55_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:15:55_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.229
Feature: Packages are up-to-date
Tags: @source
12.012
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:534 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 12.012
Command 
Command failed (pid 51592 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/tmp/tails-amd64-improve-cmd-logging@5b1848eebc+stable@688b1babda-20250717T0826Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/tmp/tails-amd64-improve-cmd-logging@5b1848eebc+stable@688b1babda-20250717T0826Z.build-manifest
ERROR: libgnutls30: the package version(3.7.9-2+deb12u5) is higher than the version on experimental (3.7.9-2+deb12u4)
INFO: Need to upgrade to a new APT snapshot:
  - b43-fwcutter (1:019-8tails1) to Debian trixie (1:019-13)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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: Tails persistence
Tags: @product @doc
1:14.264
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.008
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.526
When I try to enable persistence 1.638
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.090
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 11.593 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:28:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:28:51_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:28:51_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:28:51_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:9.801
Background
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 without a persistent partition and logged in 16.144
And I create a persistent partition with the default settings 29.255
Then the "TorConfiguration" tps feature is not enabled 4.840
When the network is plugged 0.756
And the Tor Connection Assistant autostarts 9.703
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.102
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 6.365 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:39:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:39:52_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:39:52_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:39:52_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/05:39:52_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product @doc
2:3.256
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.635
And I capture all network traffic 0.074
When I successfully start the Unsafe Browser 30.513
And I open the Tails homepage in the Unsafe Browser 16.839
And the Tails homepage loads in the Unsafe Browser 1:0.193
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:21:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.911 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 06:01:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:01:37_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:01:37_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:01:37_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:01:37_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.045
Feature: Browsing the web using the Tor Browser
Tags: @product
1:32.038
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.812
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.098
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.071
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.088
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.072
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.072
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.070
And the file "/tmp/synaptic.html" exists 0.057
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.118
When I start the Tor Browser 38.257
And the Tor Browser loads the startup page 1.120
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 18.628
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.626
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 0.643
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 8.174
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 5.123
can 
can still find TorBrowserSynapticManual.png on the screen (FindFailed)
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/common_steps.rb:757:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:65:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 6.195 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 06:17:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:17:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:17:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:17:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:17:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:57.291
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 56.688
And all tps features are active 3.095
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.540
And all persistent directories have safe access rights 3.996
When I start the Tor Browser in offline mode 52.733
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:139:in `When I start the Tor Browser in offline mode'
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 7.235 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 06:38:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:38:00_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:38:00_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:38:00_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/06:38:00_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
23:3.285
Scenario wget(1) should work for HTTPS and go through Tor
Steps
When I wget "https://example.com/" to stdout 23:3.285
Tor 
Tor operation failed (despite retrying 10 times) with
RuntimeError: wget:ing https://example.com/ failed with:

--2025-07-17 16:03:26--  https://example.com/
Resolving example.com (example.com)... 96.7.128.175
Connecting to example.com (example.com)|96.7.128.175|:443... 1752768331 ERROR torsocks[9149]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:527)
failed: Connection refused.
 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/torified_misc.rb:4:in `/^I (wget|curl) "([^"]+)" to stdout$/'
features/torified_misc.feature:8:in `When I wget "https://example.com/" to stdout'
Then the wget command is successful 0.000
And the wget standard output contains "Example Domain" 0.000
After features/support/hooks.rb:517 0.042
After features/support/hooks.rb:330 5.427 
SCENARIO FAILED: 'wget(1) should work for HTTPS and go through Tor' (at time 07:03:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:03:00_wget_1__should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:03:00_wget_1__should_work_for_HTTPS_and_go_through_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:03:00_wget_1__should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:03:00_wget_1__should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
23:0.860
Scenario curl should work for HTTPS and go through Tor
Steps
When I curl "https://example.com/" to stdout 23:0.860
Tor 
Tor operation failed (despite retrying 10 times) with
RuntimeError: curl:ing https://example.com/ failed with:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/torified_misc.rb:4:in `/^I (wget|curl) "([^"]+)" to stdout$/'
features/torified_misc.feature:13:in `When I curl "https://example.com/" to stdout'
Then the curl command is successful 0.000
And the curl standard output contains "Example Domain" 0.000
After features/support/hooks.rb:517 0.046
After features/support/hooks.rb:330 7.517 
SCENARIO FAILED: 'curl should work for HTTPS and go through Tor' (at time 07:26:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:26:26_curl_should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:26:26_curl_should_work_for_HTTPS_and_go_through_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:26:26_curl_should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:26:26_curl_should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @doc
2:0.735
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.065
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.521
When I successfully start the Unsafe Browser 31.476
When I open the Tails homepage in the Unsafe Browser 10.882
Then the Tails homepage loads in the Unsafe Browser 1:2.855
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:39:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 5.877 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 07:35:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:35:11_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:35:11_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:35:11_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/07:35:11_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
47.072
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 33.754
And I unlock and mount this VeraCrypt file container with GNOME Disks 13.318
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

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