Project Number Date
test_Tails_ISO_test-suite-trixie-2 15 13 Jun 2025, 23:07

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
56.432
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:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 45.072
When the network is plugged 11.359
Command failed (pid 7116 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.053
After features/support/hooks.rb:330 6.595

SCENARIO FAILED: 'Clock with host's time' (at time 00:29:00)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:00_Clock_with_host_s_time.journal

After features/support/hooks.rb:100 0.000
Feature: Time syncing
26.601
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 15.240
When the network is plugged 11.361
Command failed (pid 7267 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.057
After features/support/hooks.rb:330 6.787

SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:29:34)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:29:34_Clock_with_host_s_time_while_using_bridges.journal

After features/support/hooks.rb:100 0.000
Feature: Time syncing
36.359
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 10.769
When I bump the system time with "+1 day" 2.790
And I capture all network traffic 0.105
And the network is plugged 22.693
Command failed (pid 7420 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:25:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:515 0.034
After features/support/hooks.rb:330 6.297

SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:30:17)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_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_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:30:17_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal

After features/support/hooks.rb:100 0.037
Feature: Time syncing
55.874
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.364
And I make sure time sync before Tor connects times out 1.602
When the network is plugged 44.907
Command failed (pid 9129 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:58:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.047
After features/support/hooks.rb:330 6.550

SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:39:15)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:39:15_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal

After features/support/hooks.rb:100 0.001
Feature: Time syncing
53.949
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 11.545
When I bump the system time with "+8 hours +15 minutes" 0.871
And all notifications have disappeared 6.894
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.124
And the network is plugged 34.510
Command failed (pid 9279 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:68:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 0.000
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 6.724

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:40:16)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:40:16_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.039
Feature: Time syncing
56.166
Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 25.212
When I bump the system time with "+8 hours +15 minutes" 0.415
And all notifications have disappeared 9.417
And I capture all network traffic 0.004
And the network is plugged 21.117
Command failed (pid 9564 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:87:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:515 0.046
After features/support/hooks.rb:330 6.318

SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:41:19)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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_test-suite-trixie-2/15/artifact/build-artifacts/00:41:19_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.059
Feature: Time syncing
50.170
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 14.211
And I make sure time sync before Tor connects uses a fake connectivity check service 1.195
And the network is plugged 34.763
Command failed (pid 9721 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/time_syncing.feature:108:in `And the network is plugged'
And Tor is ready 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
When I make NetworkManager perform a connectivity check 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
And the HTTP requests received by the fake connectivity check service are identical 0.000
After features/support/hooks.rb:515 0.049
After features/support/hooks.rb:330 6.918

SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:42:16)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_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_test-suite-trixie-2/15/artifact/build-artifacts/00:42:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal

After features/support/hooks.rb:100 0.000
35.778
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 13.902
And I capture all network traffic 0.007
When the network is plugged 21.868
Command failed (pid 9869 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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 6.365

SCENARIO FAILED: 'Using normal bridges' (at time 00:42:58)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:42:58_Using_normal_bridges.journal

After features/support/hooks.rb:100 0.048
31.976
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 10.366
And I capture all network traffic 0.012
When the network is plugged 21.597
Command failed (pid 10019 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 6.292

SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:43:37)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:43:37_Using_obfs4_pluggable_transports.journal

After features/support/hooks.rb:100 0.040
34.783
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 13.514
And I capture all network traffic 0.002
When the network is plugged 21.266
Command failed (pid 10170 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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.489

SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:44:18)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:44:18_Using_obfs4_pluggable_transports_from_a_QR_code.journal

After features/support/hooks.rb:100 0.042
34.992
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 12.768
And I capture all network traffic 0.014
When the network is plugged 22.208
Command failed (pid 10322 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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.410

SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:45:00)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_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_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_TCA_can_scan_QR_code_after_a_connection_failure.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_TCA_can_scan_QR_code_after_a_connection_failure.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_TCA_can_scan_QR_code_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:45:00_TCA_can_scan_QR_code_after_a_connection_failure.journal

After features/support/hooks.rb:100 0.052
1:52.763
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 12.893
And I capture all network traffic 0.004
When the network is plugged 1:39.865
Command failed (pid 10471 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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.400

SCENARIO FAILED: 'Default Tor bridges' (at time 00:46:59)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:46:59_Default_Tor_bridges.journal

After features/support/hooks.rb:100 0.039
1:9.954
Background
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 11.648
And I capture all network traffic 0.002
When the network is plugged 58.302
Command failed (pid 10625 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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 7.080

SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:48:15)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_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_test-suite-trixie-2/15/artifact/build-artifacts/00:48:15_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal

After features/support/hooks.rb:100 0.031
2:37.279
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 13.885
And I capture all network traffic 0.025
When the network is plugged 2:23.369
Command failed (pid 10775 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given the Tor network and default bridges are unblocked 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 6.332

SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:51:00)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:51:00_TCA_can_reconnect_after_a_connection_failure.journal

After features/support/hooks.rb:100 0.037
1:52.098
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.046
Steps
Given I have started Tails from DVD without network and logged in 12.318
And I capture all network traffic 0.007
When the network is plugged 1:39.773
Command failed (pid 11296 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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 6.412

SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 00:52:58)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:52:58_Normal_bridges_are_not_allowed_in__Hide__mode.journal

After features/support/hooks.rb:100 0.056
53.942
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 11.183
And I capture all network traffic 0.003
When the network is plugged 42.754
Command failed (pid 11449 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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 6.565

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:53:59)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_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_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:53:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:100 0.059
34.202
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 13.052
And I capture all network traffic 0.041
When the network is plugged 21.108
Command failed (pid 11598 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
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 6.511

SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:54:39)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_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_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_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_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:54:39_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal

After features/support/hooks.rb:100 0.057
49.047
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 13.542
And I capture all network traffic 0.007
When the network is plugged 35.497
Command failed (pid 11749 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-trixie-2/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:184:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
Given the Tor network and default bridges are unblocked 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.585

SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:55:35)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_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_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_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_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:55:35_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal

After features/support/hooks.rb:100 0.065
22.080
Scenario Erasure of memory freed by killed userspace processes
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 13.195
And I prepare Tails for memory erasure tests 1.304
When I start a process allocating 128 MiB of memory with a known pattern 2.697
Then patterns cover at least 128 MiB in the guest's memory 4.882
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1

Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 6.259

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:56:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:56:04_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:56:04_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:56:04_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/00:56:04_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
12:40.674
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.004
Before features/support/hooks.rb:507 0.004
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:43.243
And I update APT using apt 14.307
And I install "popularity-contest" using apt 27.845
Then I am proposed to add the "popularity-contest" package to my Additional Software 17.091
When I create a persistent storage and activate the Additional Software feature 33.837
Then Additional Software is correctly configured for package "popularity-contest" 3.442
When I shutdown Tails and wait for the computer to power off 14.967
And I start Tails from USB drive "__internal" with network unplugged 1:59.405
And I enable persistence 32.654
And I log in to a new session 1:2.925
And the Additional Software installation service has started 28.067
Then I am notified that the installation succeeded 5:2.885
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:631:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
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:515 0.033
After features/support/hooks.rb:330 8.697

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:52:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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_test-suite-trixie-2/15/artifact/build-artifacts/01:52:59_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.010
25:39.853
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.002
Before features/support/hooks.rb:507 0.002
Steps
Given a computer 0.238
And I start Tails from USB drive "__internal" and I login with an administration password 3:19.242
And I update APT using apt 14.468
When I install "makepp" using apt 22:5.904
Tor
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./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/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211: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/apt.rb:81:in `block in <top (required)>' (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/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.060
After features/support/hooks.rb:330 5.747

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:18:48)

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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_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_test-suite-trixie-2/15/artifact/build-artifacts/02:18:48_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.010
10:58.199
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.002
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.162
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:0.529
When I uninstall "popularity-contest" using apt 25.399
And I accept removing "popularity-contest" from Additional Software 2.807
Then "popularity-contest" is not in the list of Additional Software 0.708
When I start Synaptic 16.447
And I update APT using Synaptic 22.331
And I install "cowsay" using Synaptic 4:49.812
Tor
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (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/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
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:515 0.052
After features/support/hooks.rb:330 6.792

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:29:52)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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_test-suite-trixie-2/15/artifact/build-artifacts/02:29:52_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.018
14:14.331
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.212
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:46.957
And I configure APT to prefer an old version of cowsay 0.028
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 32.513
And I accept adding "cowsay" to Additional Software 12.720
And Additional Software is correctly configured for package "cowsay" 4.136
And I shutdown Tails and wait for the computer to power off 10.401
And I start Tails from USB drive "__internal" with network unplugged 2:3.039
And I enable persistence 17.647
# 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.034
# 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.098
And I log in to a new session 1:11.420
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 36.509
And I revert the APT tweaks that made it prefer an old version of cowsay 0.071
# 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.069
And the network is plugged 0.079
And Tor is ready 26.506
And available upgrades have been checked 3.440
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.946
And I can open the Additional Software configuration window from the notification 5.998
And I shutdown Tails and wait for the computer to power off 20.809
And I start Tails from USB drive "__internal" with network unplugged 2:2.915
And I enable persistence 19.047
# 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.029
And I log in to a new session 1:2.664
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 39.139
And I revert the APT tweaks that made it prefer an old version of cowsay 0.104
And the network is plugged 0.094
And Tor is ready 15.693
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
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:515 0.061
After features/support/hooks.rb:330 5.785

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:44:14)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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_test-suite-trixie-2/15/artifact/build-artifacts/02:44:14_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.021
Tags: @product
4:29.610
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.353
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 44.738
When I start Tails from USB drive "old" with network unplugged 3:43.386
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 8.491

SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:52:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:52:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:52:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:52:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:52:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal

After features/support/hooks.rb:100 0.007
Tags: @product
2:42.466
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login 2:42.190
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 5.875

SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:55:18)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:55:18_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:55:18_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:55:18_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:55:18_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.007
Tags: @product
2:45.734
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:45.533
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 6.906

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:58:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:58:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:58:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:58:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/02:58:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.012
Tags: @product
2:26.280
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.543
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.737
The
The Dogtail init script raised: SearchError: descendant 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:283: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/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 7.069

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 03:04:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:04_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:04_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:04_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:04_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.055
41.580
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.132
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.400
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.732
When the network is plugged 0.086
And Tor is ready 15.417
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 6.722

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:04:54)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:04:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000
23:2.739
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.825
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.754
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.148
And Tor is ready 26.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:20.668
Tor
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (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/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.945

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:28:03)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:28:03_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:28:03_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:28:03_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:28:03_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000
3:7.861
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 17.054
And I prepare Tails for memory erasure tests 0.853
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 1:13.931
And I fill the USB drive with a known pattern 1.585
And I read the content of the test FS 0.102
And patterns cover at least 99% of the test FS size in the guest's memory 3.814

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I eject the boot medium 0.355
And I wait for Tails to finish wiping the memory 1:30.162
cannot find MemoryWipeCompleted.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/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.935

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:35:15)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:35:15_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:35:15_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:35:15_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal

After features/support/hooks.rb:100 0.001
Tags: @product
1:37.091
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.768
# 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 14.385
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.818
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.645
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.064
When I start Tails' custom backup tool 5.926
Then the backup tool displays "Plug in your backup Tails USB stick" 0.551
When I plug USB drive "backup" 8.615
And I give the Persistent Storage on drive "backup" its own UUID 0.206
And I click "Retry" in the backup tool 1.436
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.378
When I click "Back Up" in the backup tool 1.283
And I enter my persistent storage passphrase into the polkit prompt 21.010
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:822:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
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 11.982

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:41:43)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:41:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:41:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/03:41:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.303
Tags: @product
18.627
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 13.553
Then the keys trusted by APT are valid for the next 3 months 5.074
The
The following APT key(s) will not be valid in 3 months: D051FE3A848DCABD4625787A6FFA8EF91DB114E0, 4C7A8E5E9454FE3FAE1E78ADF1D53D8C4F368D5D, C20CA1D9499DECBBD8BDACF9E415B2B4B5F5BBED, 4E6CBA363A3A3708DC533C75B7A50B4134FC6FE5, 084750FC01A6D388A643D869010908312D230C5F, A99951DAF9BB569BDB50AD90A70DAF536070D3A1, 6039406A4EDCE124CF087B0AEC61E0B0BBE55AB3, 0F8A1F54CB8BF69B34DB847F0A3B614236CA98F3, 150C8614919D8446E01E83AF9AA38DCD55BE302B, 7F5A44454C724A65CBCD4FB14D270D06F42584E6, F6CFDE3061333CE2A43FDAF0DFD993306D849617, 0E4EDE2C7F3E1FC0D033800E64481591B98321F9, 9FED2BCBDCD29CDF762678CBAED4B06F473041FA, A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553, ED6D65271AACF0FF15D123036FB2A1C265FFB764, 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1, 126C0D24BD8A2942CC7DF8AC7638D0442B90D010, D21169141CECD440F2EB8DDA9D6D8F6BC857C906, 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500, E1CF20DDFFE4B89E802658F1E0B11894F66AEC98, 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC, 6ED6F5CB5FA6FB2F460AE88EEDA0D2388AE22BA9, 379483D8B60160B155B372DDAA8E81B4331F7F50.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:40:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:330 5.843

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:28:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:28:01_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:28:01_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:28:01_The_included_APT_repository_keys_are_up-to-date.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:28:01_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
1:27.951
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.356
When I log in to a new session in Chinese (zh_CN) 59.678
Then the keyboard layout is set to "cn" 0.796
When the network is plugged 0.155
And Tor is ready 14.965
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/localization.feature:44:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.720

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:42:14)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:42:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:42:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:42:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:42:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
1:27.000
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.719
When I log in to a new session in German (de) 1:0.301
Then the keyboard layout is set to "de" 1.303
When the network is plugged 0.761
And Tor is ready 14.914
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/localization.feature:47:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "de" 0.000
After features/support/hooks.rb:330 5.868

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:51:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:51:34_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:51:34_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:51:34_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:51:34_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
1:28.845
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.467
When I log in to a new session in Indonesian (id) 58.622
Then the keyboard layout is set to "id" 0.319
When the network is plugged 0.191
And Tor is ready 15.244
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/localization.feature:49:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 5.525

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:57:13)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:57:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:57:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:57:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/04:57:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
5:5.517
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:10.440
Then Tails is running from USB drive "__internal" 1.260
When I create a file in the Persistent directory 0.155
And I create a persistent partition with the default settings 45.919
Then the file I created was copied to the Persistent Storage 4.148
When I shutdown Tails and wait for the computer to power off 24.239
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.353
cannot find TailsGreeter.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:477:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/persistence.feature:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 7.071

SCENARIO FAILED: 'Creating a Persistent Storage' (at time 05:50:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/05:50:41_Creating_a_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/05:50:41_Creating_a_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/05:50:41_Creating_a_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/05:50:41_Creating_a_Persistent_Storage.journal

After features/support/hooks.rb:100 0.020
Tags: @product
5:48.489
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.163
And the network is plugged 0.171
And Tor is ready 28.280
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.572
And I shutdown Tails and wait for the computer to power off 18.497
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:17.857
And I capture all network traffic 0.207
And the network is plugged 2.030
And Tor is ready 27.708
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:639:in `/^Tor is ready$/'
features/persistence.feature:91:in `And Tor is ready'
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 8.346

SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 06:07:44)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:07:44_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:07:44_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:07:44_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:07:44_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.127
Tags: @product
7:17.915
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 17.526
When I enable persistence 1:18.149
Then no persistent Greeter options were restored 17.047
When I set all Greeter options to non-default values 58.192
And I log in to a new session in German (de) after having activated the Persistent Storage 1:2.801
Then all Greeter options are set to non-default values 0.243
When I cold reboot the computer 19.010
And the computer reboots Tails 2:17.741
Given I enable persistence 28.543
Then persistent Greeter options were restored 0.651
When I log in to a new session after having activated the Persistent Storage 18.007
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:513:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 8.258

SCENARIO FAILED: 'Persistent Greeter options' (at time 06:17:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:17:05_Persistent_Greeter_options.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:17:05_Persistent_Greeter_options.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:17:05_Persistent_Greeter_options.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:17:05_Persistent_Greeter_options.journal

After features/support/hooks.rb:100 0.014
Tags: @product
7:19.063
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.554
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 1:9.722
And I shutdown Tails and wait for the computer to power off 22.854
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 4:25.785
And I change the passphrase of the Persistent Storage back to the original 1:7.146
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:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:124:in `And I change the passphrase of the Persistent Storage back to the original'
After features/support/hooks.rb:330 8.810

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 06:24:33)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:24:33_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:24:33_Changing_the_Persistent_Storage_passphrase.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:24:33_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:100 0.008
Tags: @product
1:20.182
Scenario Feature activation fails
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 and stopped at Tails Greeter's login screen 19.709
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.105
When I try to enable persistence 0.366
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.000
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 25.332

SCENARIO FAILED: 'Feature activation fails' (at time 06:33:59)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:33:59_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:33:59_Feature_activation_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:33:59_Feature_activation_fails.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:38.661
Scenario Manual filesystem repair is successful
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 and stopped at Tails Greeter's login screen 20.055
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.188
When I try to enable persistence 1.414
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.003
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 25.360

SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 06:49:14)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:49:14_Manual_filesystem_repair_is_successful.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:49:14_Manual_filesystem_repair_is_successful.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:49:14_Manual_filesystem_repair_is_successful.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:17.122
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.073
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 16.726
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.104
When I try to enable persistence 0.289
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.002
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 25.161

SCENARIO FAILED: 'Manual filesystem repair fails' (at time 06:50:59)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:50:59_Manual_filesystem_repair_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:50:59_Manual_filesystem_repair_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:50:59_Manual_filesystem_repair_fails.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:35.390
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.091
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 15.936
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.073
And Tails detects disk read failures on the boot device 1.844
When I try to enable persistence 1.418
Then the Welcome Screen tells me that my hardware is probably failing 1:0.117
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:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 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 18.878

SCENARIO FAILED: 'Filesystem and I/O errors' (at time 06:52:59)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:52:59_Filesystem_and_I_O_errors.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:52:59_Filesystem_and_I_O_errors.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/06:52:59_Filesystem_and_I_O_errors.journal

After features/support/hooks.rb:100 0.000
1:19.630
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.171
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:19.630
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistent_tor_bridges.feature:8:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And I create a persistent partition with the default settings 0.000
Then the "TorConfiguration" tps feature is not enabled 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 7.277

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 07:03:38)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:03:38_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:03:38_Disabling_persistence_of_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:03:38_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:03:38_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
1:27.809
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 22.693
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.982
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.679
When I accept the autoconfiguration wizard's configuration 39.434
And I send an email to myself 13.151
And I fetch my email 3.623
Then I can find the email I sent to myself in my inbox 7.243
Hooks
After features/support/hooks.rb:515 4.099
execution expired (RemoteShell::Timeout)
./features/support/helpers/firewall_helper.rb:135:in `pcap_connections_helper'
./features/support/helpers/firewall_helper.rb:163:in `assert_all_connections'
./features/support/helpers/firewall_helper.rb:178:in `assert_no_leaks'
./features/support/hooks.rb:524:in `After'
After features/support/hooks.rb:330 8.881

SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 07:25:54)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:25:54_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:25:54_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:25:54_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:100 0.001
Tags: @product
48.788
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 17.033
Then the Tor Connection Assistant reports that I am not connected to a local network 10.641
When I plug a Wi-Fi adapter 2.215
Then Tor Connection suggests me to connect to Wi-Fi 2.680
And I click on the Wi-Fi settings 1.343
And The Wi-Fi settings are displayed 14.874
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'gnome-control-center' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/tor.rb:1110:in `new'
./features/step_definitions/tor.rb:1110:in `/^The Wi-Fi settings are displayed$/'
features/tor_connection.feature:15:in `And The Wi-Fi settings are displayed'
After features/support/hooks.rb:330 7.221

SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 07:27:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:27:22_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:27:22_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:27:22_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:27:22_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal

After features/support/hooks.rb:100 0.000
Tags: @product
40.404
Scenario The system DNS is always set up to use Tor's DNSPort
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.088
Steps
Given I have started Tails from DVD without network and logged in 19.761
And the system DNS is using the local DNS resolver 0.934
And the network is plugged 2.670
And I successfully configure Tor 17.036
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:685:in `/^I successfully configure Tor$/'
features/tor_enforcement.feature:69:in `And I successfully configure Tor'
Then the system DNS is still using the local DNS resolver 0.000
After features/support/hooks.rb:330 8.274

SCENARIO FAILED: 'The system DNS is always set up to use Tor's DNSPort' (at time 07:38:58)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:38:58_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:38:58_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:38:58_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:38:58_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.journal

After features/support/hooks.rb:100 0.000
1:38.251
Scenario Playing an Ogg audio track
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 58.932
When I start the Tor Browser 39.318
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:38:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I can listen to an Ogg audio track in Tor Browser 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 17.384

SCENARIO FAILED: 'Playing an Ogg audio track' (at time 07:53:23)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:53:23_Playing_an_Ogg_audio_track.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:53:23_Playing_an_Ogg_audio_track.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:53:23_Playing_an_Ogg_audio_track.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:37.695
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.146
Steps
Given I have started Tails from DVD and logged in and the network is connected 22.078
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.405
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.189
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.376
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.244
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.130
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.121
And the file "/tmp/synaptic.html" exists 0.111
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.268
When I start the Tor Browser 41.465
And the Tor Browser loads the startup page 1.865
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 41.826
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.767
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 8.072
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 20.111
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 4.943
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 8.802
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 5.916
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:788:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:67:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 7.270

SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 07:58:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:58:16_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_test-suite-trixie-2/15/artifact/build-artifacts/07:58:16_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:58:16_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/07:58:16_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal

After features/support/hooks.rb:100 0.000
1:18.625
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Before features/support/hooks.rb:507 0.017
Steps
Given I have started Tails from DVD and logged in and the network is connected 39.855
When I start the Tor Browser 38.770
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:81:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
When I open the address "https://example.com/" in the Tor Browser 0.000
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 0.000
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads the startup page 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 14.020

SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 08:01:42)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:01:42_The_Tor_Browser_s__New_identity__feature_works_as_expected.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:01:42_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:01:42_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:1.443
Scenario WebRTC is disabled in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.392
When I start the Tor Browser 44.051
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:98:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
When I open the address "https://net.ipcalf.com/" in the Tor Browser 0.000
Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page 0.000
When I open the address "https://mozilla.github.io/webrtc-landing/pc_test.html" in the Tor Browser 0.000
Then Tor Browser displays a "RTCPeerConnection is missing!" heading on the "Simple RTCPeerConnection Video Test" page 0.000
After features/support/hooks.rb:330 17.096

SCENARIO FAILED: 'WebRTC is disabled in Tor Browser' (at time 08:04:43)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:04:43_WebRTC_is_disabled_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:04:43_WebRTC_is_disabled_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:04:43_WebRTC_is_disabled_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:19.142
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:19.142
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81: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/torified_browsing.feature:106:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And I successfully configure Tor 0.000
And available upgrades have been checked 0.000
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 6.402

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 08:06:19)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:06:19_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:06:19_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:06:19_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:06:19_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:15.605
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 1:15.605
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/torified_browsing.feature:127:in `Given I have started Tails from DVD without network and logged in'
features/torified_browsing.feature:120:in `Given I have started Tails from DVD without network and logged in'
Then the live user's Documents directory exists 0.000
And there is a GNOME bookmark for the Documents directory 0.000
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Documents GNOME bookmark 0.000
After features/support/hooks.rb:330 6.472

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 08:07:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:07:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:07:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:07:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:07:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:56.699
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.172
Steps
Given I have started Tails from DVD without network and logged in 22.510
Then the live user's Music directory exists 1.165
And there is a GNOME bookmark for the Music directory 22.052
Then I start the Tor Browser in offline mode 29.208
And I can save the current page as "index.html" to the Music GNOME bookmark 41.762
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `And I can save the current page as "index.html" to the Music GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 17.300

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 08:12:18)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:12:18_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:12:18_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:12:18_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:0.399
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 22.827
Then the live user's Pictures directory exists 2.638
And there is a GNOME bookmark for the Pictures directory 23.723
Then I start the Tor Browser in offline mode 30.463
And I can save the current page as "index.html" to the Pictures GNOME bookmark 40.745
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:130:in `And I can save the current page as "index.html" to the Pictures GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 17.331

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 08:14:38)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:14:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:14:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:14:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:14:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:23.103
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.103
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81: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/torified_browsing.feature:134:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And all tps features are active 0.000
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories have safe access rights 0.000
When I start the Tor Browser in offline mode 0.000
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.222

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 08:18:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:18:42_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:18:42_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:18:42_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:18:42_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
1:13.447
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 1:13.447
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81: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/totem.feature:12:in `Given I have started Tails from DVD without network and logged in'
And I plug and mount a USB drive containing sample videos 0.000
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.000
And the file "/home/amnesia/video.mp4" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I open "/home/amnesia/video.mp4" with Totem 0.000
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 0.000
Given I close Totem 0.000
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /usr/lib/live/mount/overlay.
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And I copy "/home/amnesia/video.mp4" to "/home/amnesia/.purple/otr.private_key" as user "amnesia" 0.000
And the file "/home/amnesia/.purple/otr.private_key" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/home/amnesia/.purple/otr.private_key" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.purple/otr.private_key" 0.000
After features/support/hooks.rb:330 6.957

SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 08:23:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:23:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:23:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:23:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:23:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
1:35.382
Scenario Starting the Unsafe Browser works as it should
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 37.336
When I successfully start the Unsafe Browser 42.254
Then the Unsafe Browser runs as the expected user 3.289
And the Unsafe Browser has a red theme 12.501
cannot find UnsafeBrowserRedTheme.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/unsafe_browser.rb:51:in `/^the Unsafe Browser has a red theme$/'
features/unsafe_browser.feature:28:in `And the Unsafe Browser has a red theme'
And the Unsafe Browser shows a warning as its start page 0.000
And the Unsafe Browser has no add-ons installed 0.000
And the Unsafe Browser has no bookmarks 0.000
And the Unsafe Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.813

SCENARIO FAILED: 'Starting the Unsafe Browser works as it should' (at time 08:32:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:32:42_Starting_the_Unsafe_Browser_works_as_it_should.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:32:42_Starting_the_Unsafe_Browser_works_as_it_should.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:32:42_Starting_the_Unsafe_Browser_works_as_it_should.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:32:42_Starting_the_Unsafe_Browser_works_as_it_should.journal

After features/support/hooks.rb:100 0.000
2:1.308
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 37.692
When I successfully start the Unsafe Browser 41.833
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.006

Slept for 10 seconds

And I try to start the Unsafe Browser 1.571
Then I see a warning about another instance already running 30.203
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76: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/unsafe_browser.rb:75:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/unsafe_browser.rb:75:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 11.785

SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 08:37:44)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:37:44_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:37:44_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/15/artifact/build-artifacts/08:37:44_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal

After features/support/hooks.rb:100 0.000