Project Number Date
test_Tails_ISO_test-suite-trixie-2 9 13 Jun 2025, 00:28

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
10:10.764
Scenario Clock with host's time
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 8.773
When the network is plugged 10:1.990
Command 
Command failed (pid 7182 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]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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.073
After features/support/hooks.rb:330 7.200 
SCENARIO FAILED: 'Clock with host's time' (at time 00:27:28)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:27:28_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:27:28_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/9/artifact/build-artifacts/00:27:28_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:27:28_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:27:28_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:27:28_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.983
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.002
Steps
Given I have started Tails from DVD without network and logged in 8.569
When the network is plugged 10:1.414
Command 
Command failed (pid 7345 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]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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.056
After features/support/hooks.rb:330 7.453 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:37:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:37:46_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/9/artifact/build-artifacts/00:37:46_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/9/artifact/build-artifacts/00:37:46_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:37:46_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:37:46_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:37:46_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.944
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.004
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.065
When I bump the system time with "+1 day" 0.309
And I capture all network traffic 0.003
And the network is plugged 10:0.565
Command 
Command failed (pid 7515 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]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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.050
After features/support/hooks.rb:330 7.551 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:48:03)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/00:48:03_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/9/artifact/build-artifacts/00:48:03_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/9/artifact/build-artifacts/00:48:03_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/9/artifact/build-artifacts/00:48:03_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/9/artifact/build-artifacts/00:48:03_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/9/artifact/build-artifacts/00:48:03_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.048
Feature: Time syncing
Tags: @product @check_tor_leaks
10:11.757
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.010
Before features/support/hooks.rb:507 0.012
Steps
Given I have started Tails from DVD without network and logged in 9.398
And I make sure time sync before Tor connects times out 1.158
When the network is plugged 10:1.201
Command 
Command failed (pid 9511 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]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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.044
After features/support/hooks.rb:330 7.385 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 01:05:02)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:05:02_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/9/artifact/build-artifacts/01:05:02_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/9/artifact/build-artifacts/01:05:02_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/9/artifact/build-artifacts/01:05:02_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/9/artifact/build-artifacts/01:05:02_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/9/artifact/build-artifacts/01:05:02_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.002
Feature: Time syncing
Tags: @product @check_tor_leaks
2:25.430
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.014
Before features/support/hooks.rb:507 0.037
Steps
Given I have started Tails from DVD without network and logged in 10.171
When I bump the system time with "+8 hours +15 minutes" 0.302
And all notifications have disappeared 5.374
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.099
And the network is plugged 2:9.478
Command 
Command failed (pid 9677 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.035
After features/support/hooks.rb:330 6.878 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 01:07:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:07:35_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/9/artifact/build-artifacts/01:07:35_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/9/artifact/build-artifacts/01:07:35_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/9/artifact/build-artifacts/01:07:35_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/9/artifact/build-artifacts/01:07:35_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/9/artifact/build-artifacts/01:07:35_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.052
Feature: Time syncing
Tags: @product @check_tor_leaks
10:16.846
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.023
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.358
When I bump the system time with "+8 hours +15 minutes" 0.302
And all notifications have disappeared 6.259
And I capture all network traffic 0.003
And the network is plugged 10:0.922
Command 
Command failed (pid 9832 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]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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.038
After features/support/hooks.rb:330 7.225 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 01:17:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:17:59_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/9/artifact/build-artifacts/01:17:59_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/9/artifact/build-artifacts/01:17:59_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/9/artifact/build-artifacts/01:17:59_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/9/artifact/build-artifacts/01:17:59_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/9/artifact/build-artifacts/01:17:59_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.036
Feature: Time syncing
Tags: @product @check_tor_leaks
1:8.287
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 11.489
And I make sure time sync before Tor connects uses a fake connectivity check service 1.248
And the network is plugged 55.549
Command 
Command failed (pid 10002 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.043
After features/support/hooks.rb:330 6.826 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 01:19:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:19:15_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/9/artifact/build-artifacts/01:19:15_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/9/artifact/build-artifacts/01:19:15_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/9/artifact/build-artifacts/01:19:15_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/9/artifact/build-artifacts/01:19:15_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/9/artifact/build-artifacts/01:19:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.000
Feature: Using Tor bridges and pluggable transports
51.797
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 10.215
And I capture all network traffic 0.003
When the network is plugged 41.578
Command 
Command failed (pid 10151 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
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 7.042 
SCENARIO FAILED: 'Using normal bridges' (at time 01:20:13)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:20:13_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.044
Feature: Using Tor bridges and pluggable transports
10:12.756
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 11.664
And I capture all network traffic 0.003
When the network is plugged 10:1.088
Command 
Command failed (pid 10303 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]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :    0, 004ba                    , desc                          , Not in dir file
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 7.170 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 01:30:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:30:33_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.040
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
19.133
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails from DVD without network and logged in 8.942
And I prepare Tails for memory erasure tests 0.575
When I start a process allocating 128 MiB of memory with a known pattern 2.394
Then patterns cover at least 128 MiB in the guest's memory 7.220
99.610% 
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.547 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 01:41:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:41:31_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/9/artifact/build-artifacts/01:41:31_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:41:31_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/01:41:31_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
12:0.627
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.003
Before features/support/hooks.rb:507 0.007
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:32.948
And I update APT using apt 11.148
And I install "popularity-contest" using apt 27.068
Then I am proposed to add the "popularity-contest" package to my Additional Software 8.553
When I create a persistent storage and activate the Additional Software feature 22.355
Then Additional Software is correctly configured for package "popularity-contest" 2.928
When I shutdown Tails and wait for the computer to power off 14.054
And I start Tails from USB drive "__internal" with network unplugged 1:52.444
And I enable persistence 32.581
And I log in to a new session 58.377
And the Additional Software installation service has started 34.874
Then I am notified that the installation succeeded 5:3.292
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:628: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.032
After features/support/hooks.rb:330 8.971 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 02:33:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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/9/artifact/build-artifacts/02:33:18_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.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:26.207
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.011
Before features/support/hooks.rb:507 0.008
Steps
Given a computer 0.220
And I start Tails from USB drive "__internal" and I login with an administration password 3:7.829
And I update APT using apt 12.186
When I install "makepp" using apt 22:5.971
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.047
After features/support/hooks.rb:330 5.312 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:58:54)
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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_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/9/artifact/build-artifacts/02:58:54_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:25.455
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.003
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.151
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:39.978
When I uninstall "popularity-contest" using apt 25.222
And I accept removing "popularity-contest" from Additional Software 2.709
Then "popularity-contest" is not in the list of Additional Software 1.250
When I start Synaptic 16.683
And I update APT using Synaptic 21.975
And I install "cowsay" using Synaptic 4:37.482
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.041
After features/support/hooks.rb:330 6.890 
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 03:09:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_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/9/artifact/build-artifacts/03:09:25_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
3:31.975
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.152
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 35.577
When I start Tails from USB drive "old" with network unplugged 2:55.163
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb: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 7.888 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 03:32:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/03:32:31_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/9/artifact/build-artifacts/03:32:31_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/9/artifact/build-artifacts/03:32:31_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/9/artifact/build-artifacts/03:32:31_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:40.230
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.003
Steps
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 2:40.011
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb: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.796 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 03:35:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/03:35:19_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/9/artifact/build-artifacts/03:35:19_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/9/artifact/build-artifacts/03:35:19_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/9/artifact/build-artifacts/03:35:19_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:30.719
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.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.541
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb: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 5.768 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 03:37:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/03:37:56_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/9/artifact/build-artifacts/03:37:56_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/9/artifact/build-artifacts/03:37:56_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/9/artifact/build-artifacts/03:37:56_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:9.523
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.153
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.370
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 6.890 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 03:43:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/03:43:21_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/9/artifact/build-artifacts/03:43:21_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/9/artifact/build-artifacts/03:43:21_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/9/artifact/build-artifacts/03:43:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.047
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:57.288
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.027
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.100
And no SquashFS delta is installed 0.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.582
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.560
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.076
And Tor is ready 30.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.020
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:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
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.082 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 04:06:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:06:25_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/9/artifact/build-artifacts/04:06:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:06:25_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/9/artifact/build-artifacts/04:06:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:55.365
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.612
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.105
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 29.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.108
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.816 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 04:29:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:29:27_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/9/artifact/build-artifacts/04:29:27_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:29:27_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:29:27_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:15.000
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 13.699
# 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 13.316
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.402
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.534
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.057
When I start Tails' custom backup tool 5.608
Then the backup tool displays "Plug in your backup Tails USB stick" 0.468
When I plug USB drive "backup" 3.939
And I give the Persistent Storage on drive "backup" its own UUID 0.315
And I click "Retry" in the backup tool 1.282
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.879
When I click "Back Up" in the backup tool 1.210
And I enter my persistent storage passphrase into the polkit prompt 21.286
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:819: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 12.508 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 04:38:42)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/04:38:42_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/9/artifact/build-artifacts/04:38:42_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/9/artifact/build-artifacts/04:38:42_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.165
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
8.718
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.020
Steps
Given I have started Tails from DVD without network and logged in 8.633
Then the keys trusted by APT are valid for the next 3 months 0.085
Command 
Command failed: apt-key adv --batch --with-colons --fingerprint --list-key
error code: 127
stdout: 
stderr: /bin/sh: 1: apt-key: not found
.
<false> is not true. (ExecutionFailedInVM)
./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/checks.rb:19: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.877 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 05:15:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:15:24_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/9/artifact/build-artifacts/05:15:24_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:15:24_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/9/artifact/build-artifacts/05:15:24_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:15.682
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.002
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.904
When I log in to a new session in Persian (fa) 48.725
Then the keyboard layout is set to "ir" 0.161
When the network is plugged 0.074
And Tor is ready 23.609
Then I successfully start the Unsafe Browser 17.154
And I kill the Unsafe Browser 7.263
When I enable the screen keyboard 0.155
Then the screen keyboard works in Tor Browser 30.633
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1075:in `launch_app'
./features/step_definitions/common_steps.rb:1130:in `launch_tor_browser'
./features/step_definitions/browser.rb:472:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:51:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ir" 0.000
After features/support/hooks.rb:330 8.037 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 05:49:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:49:54_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:49:54_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:49:54_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:16.703
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.662
When I log in to a new session in Russian (ru) 49.824
Then the keyboard layout is set to "ru" 0.216
When the network is plugged 0.062
And Tor is ready 22.067
Then I successfully start the Unsafe Browser 17.802
And I kill the Unsafe Browser 7.419
When I enable the screen keyboard 0.114
Then the screen keyboard works in Tor Browser 30.533
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1075:in `launch_app'
./features/step_definitions/common_steps.rb:1130:in `launch_tor_browser'
./features/step_definitions/browser.rb:472:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:53:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ru" 0.000
After features/support/hooks.rb:330 10.650 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 05:55:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:55:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:55:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/05:55:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
50.217
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.299
And I create a persistent partition with the default settings 24.101
Then the "TorConfiguration" tps feature is not enabled 3.026
When the network is plugged 0.123
And the Tor Connection Assistant autostarts 6.728
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 5.938
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:637:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.522 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 07:13:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:13:29_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/9/artifact/build-artifacts/07:13:29_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:13:29_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:13:29_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
11.806
Scenario No unexpected error messages in the journal after booting from DVD
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.564
Then there are no unexpected messages of priority "err" or higher in the journal 0.241
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743126582953",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "3369885e7fa5454bb789afa4f80d7738",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=366;b=743f758e56da460781feb679b28b944c;m=db117e;t=63761d18216ca;x=7e276df620722794",
    "__MONOTONIC_TIMESTAMP": "14356862",
    "__REALTIME_TIMESTAMP": "1749743126582986",
    "__SEQNUM": "870",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743126583271",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "3369885e7fa5454bb789afa4f80d7738",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=368;b=743f758e56da460781feb679b28b944c;m=db17c9;t=63761d1821d16;x=2cb83859f77380f0",
    "__MONOTONIC_TIMESTAMP": "14358473",
    "__REALTIME_TIMESTAMP": "1749743126584598",
    "__SEQNUM": "872",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2263",
    "SYSLOG_TIMESTAMP": "Jun 12 15:45:34 ",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2263",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743134672582",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "2e57821b38154ce4ac13b9c34d048803",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=404;b=743f758e56da460781feb679b28b944c;m=15681a5;t=63761d1fd86f2;x=21d9f338992580cc",
    "__MONOTONIC_TIMESTAMP": "22446501",
    "__REALTIME_TIMESTAMP": "1749743134672626",
    "__SEQNUM": "1028",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743323477714",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "3369885e7fa5454bb789afa4f80d7738",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=8f1;b=743f758e56da460781feb679b28b944c;m=683a479;t=63761dd3e7777;x=cd457dbf85aa87bf",
    "__MONOTONIC_TIMESTAMP": "109290617",
    "__REALTIME_TIMESTAMP": "1749743323477879",
    "__SEQNUM": "2289",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743323477751",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "3369885e7fa5454bb789afa4f80d7738",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=8f3;b=743f758e56da460781feb679b28b944c;m=683a71a;t=63761dd3e7a19;x=dd2999e51020f8bc",
    "__MONOTONIC_TIMESTAMP": "109291290",
    "__REALTIME_TIMESTAMP": "1749743323478553",
    "__SEQNUM": "2291",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "6824",
    "SYSLOG_TIMESTAMP": "Jun 12 15:48:48 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "743f758e56da460781feb679b28b944c",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "6824",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749743328778337",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "fa0b541350c04b938ac4a61b0f209349",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=2f0738a4e2f94230b0415f688054a354;i=125d;b=743f758e56da460781feb679b28b944c;m=6d4856c;t=63761dd8f586b;x=7f4f3223fef47c9b",
    "__MONOTONIC_TIMESTAMP": "114591084",
    "__REALTIME_TIMESTAMP": "1749743328778347",
    "__SEQNUM": "4701",
    "__SEQNUM_ID": "2f0738a4e2f94230b0415f688054a354"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 6.048 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 07:18:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:18:58_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:18:58_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:18:58_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:18:58_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
14.815
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.706
Then there are no unexpected messages of priority "err" or higher in the journal 0.108
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749151451256",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "526eb5e7c7884e8c82b39d004c5e9d59",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=36a;b=bddf898288e14d13bd655ad862b673dd;m=ea5ae3;t=63763389e48aa;x=3592670c898bf9cd",
    "__MONOTONIC_TIMESTAMP": "15358691",
    "__REALTIME_TIMESTAMP": "1749749151451306",
    "__SEQNUM": "874",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749151451283",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "526eb5e7c7884e8c82b39d004c5e9d59",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=36c;b=bddf898288e14d13bd655ad862b673dd;m=ea5b96;t=63763389e495f;x=9b22a95c37c1597b",
    "__MONOTONIC_TIMESTAMP": "15358870",
    "__REALTIME_TIMESTAMP": "1749749151451487",
    "__SEQNUM": "876",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2585",
    "SYSLOG_TIMESTAMP": "Jun 12 17:25:59 ",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2585",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749159811547",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "b725a8dec601450b91fc7f38d3ea5876",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=416;b=bddf898288e14d13bd655ad862b673dd;m=169ec38;t=63763391dd9ff;x=67df051d9738bb9e",
    "__MONOTONIC_TIMESTAMP": "23718968",
    "__REALTIME_TIMESTAMP": "1749749159811583",
    "__SEQNUM": "1046",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749304835524",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "526eb5e7c7884e8c82b39d004c5e9d59",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=eb9;b=bddf898288e14d13bd655ad862b673dd;m=9cace07;t=6376341c2bdd1;x=772b790c875f1dea",
    "__MONOTONIC_TIMESTAMP": "164285959",
    "__REALTIME_TIMESTAMP": "1749749304835537",
    "__SEQNUM": "3769",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749304835897",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "526eb5e7c7884e8c82b39d004c5e9d59",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=ebb;b=bddf898288e14d13bd655ad862b673dd;m=9cad66d;t=6376341c2c638;x=30ce855af9964e31",
    "__MONOTONIC_TIMESTAMP": "164288109",
    "__REALTIME_TIMESTAMP": "1749749304837688",
    "__SEQNUM": "3771",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12755",
    "SYSLOG_TIMESTAMP": "Jun 12 17:28:33 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "bddf898288e14d13bd655ad862b673dd",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "12755",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749749313319882",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "90a1a23f0c4845e0b4576ed596b354b0",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=1839515f17ce4613b5dbdfa81e5af35b;i=18be;b=bddf898288e14d13bd655ad862b673dd;m=a4c462f;t=63763424435fa;x=92389ac50ea67d42",
    "__MONOTONIC_TIMESTAMP": "172770863",
    "__REALTIME_TIMESTAMP": "1749749313320442",
    "__SEQNUM": "6334",
    "__SEQNUM_ID": "1839515f17ce4613b5dbdfa81e5af35b"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:25:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.841 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 07:19:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:19:18_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:19:18_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:19:18_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:19:18_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
29:25.986
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 14.640
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.372
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.403
When I accept the autoconfiguration wizard's configuration 29:10.569
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired (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/thunderbird.rb:136:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:515 0.056
After features/support/hooks.rb:330 10.651 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 07:53:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:53:58_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/9/artifact/build-artifacts/07:53:58_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/9/artifact/build-artifacts/07:53:58_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000