Project Number Date
test_Tails_ISO_arti-1.4.3 12 18 May 2025, 01:54

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.428
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.282
When the network is plugged 10:1.146
Command 
Command failed (pid 13709 exit 255): ["/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :    0, starting                 , Starting
test001auth  :    0, starting                 , Starting
test002auth  :  100, done                     , Done
test003ba    :    0, starting                 , Starting
test004relay :   95, circuit_create           , Establishing a Tor circuit
test005relay :   95, circuit_create           , Establishing a Tor circuit
test006relay :   95, circuit_create           , Establishing a Tor circuit
test007relay :   95, circuit_create           , Establishing a Tor circuit
test008relay :   95, circuit_create           , Establishing a Tor circuit
test009relay :   95, circuit_create           , Establishing a Tor circuit
test010relay :   95, circuit_create           , Establishing a Tor circuit
test011relay :   95, circuit_create           , Establishing a Tor circuit
test012relay :   95, circuit_create           , Establishing a Tor circuit
test013relay :   95, circuit_create           , Establishing a Tor circuit
test014relay :   95, circuit_create           , Establishing a Tor circuit
test015relay :   95, circuit_create           , Establishing a Tor circuit
test016relay :   95, circuit_create           , Establishing a Tor circuit
test017relay :   95, circuit_create           , Establishing a Tor circuit
test018relay :   95, circuit_create           , Establishing a Tor circuit
test019bridge:   95, circuit_create           , Establishing a Tor circuit
test020bridge:   95, circuit_create           , Establishing a Tor circuit
test021obfs4 :   95, circuit_create           , Establishing a Tor circuit
test022obfs4 :   95, circuit_create           , Establishing a Tor circuit
test023defbr :   95, circuit_create           , Establishing a Tor circuit
test024client:   95, circuit_create           , Establishing a Tor circuit
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
test003ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test005relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test006relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test007relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test008relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test009relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test010relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test011relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test012relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test013relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test014relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test015relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test016relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test017relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test018relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test019bridge:    0, 003ba                    , desc                          , Not in dir file
test020bridge:    0, 003ba                    , desc                          , Not in dir file
test021obfs4 :    0, 003ba                    , desc                          , Not in dir file
test022obfs4 :    0, 003ba                    , desc                          , Not in dir file
test023defbr :    0, 003ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:151:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:143:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 5.556 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:21:16_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.800
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.438
When the network is plugged 10:1.362
Command 
Command failed (pid 13868 exit 255): ["/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :    0, starting                 , Starting
test001auth  :    0, starting                 , Starting
test002auth  :  100, done                     , Done
test003ba    :    0, starting                 , Starting
test004relay :   95, circuit_create           , Establishing a Tor circuit
test005relay :   95, circuit_create           , Establishing a Tor circuit
test006relay :   95, circuit_create           , Establishing a Tor circuit
test007relay :   95, circuit_create           , Establishing a Tor circuit
test008relay :   95, circuit_create           , Establishing a Tor circuit
test009relay :   95, circuit_create           , Establishing a Tor circuit
test010relay :   95, circuit_create           , Establishing a Tor circuit
test011relay :   95, circuit_create           , Establishing a Tor circuit
test012relay :   95, circuit_create           , Establishing a Tor circuit
test013relay :   95, circuit_create           , Establishing a Tor circuit
test014relay :   95, circuit_create           , Establishing a Tor circuit
test015relay :   95, circuit_create           , Establishing a Tor circuit
test016relay :   95, circuit_create           , Establishing a Tor circuit
test017relay :   95, circuit_create           , Establishing a Tor circuit
test018relay :   95, circuit_create           , Establishing a Tor circuit
test019bridge:   95, circuit_create           , Establishing a Tor circuit
test020bridge:   95, circuit_create           , Establishing a Tor circuit
test021obfs4 :   95, circuit_create           , Establishing a Tor circuit
test022obfs4 :   95, circuit_create           , Establishing a Tor circuit
test023defbr :   95, circuit_create           , Establishing a Tor circuit
test024client:   95, circuit_create           , Establishing a Tor circuit
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
test003ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test005relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test006relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test007relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test008relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test009relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test010relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test011relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test012relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test013relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test014relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test015relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test016relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test017relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test018relay :    0, all nodes                , desc md md_cons ns_cons       , Not in dir file
test019bridge:    0, 003ba                    , desc                          , Not in dir file
test020bridge:    0, 003ba                    , desc                          , Not in dir file
test021obfs4 :    0, 003ba                    , desc                          , Not in dir file
test022obfs4 :    0, 003ba                    , desc                          , Not in dir file
test023defbr :    0, 003ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:151:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:143:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.056
After features/support/hooks.rb:330 5.560 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:31:32)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:31:32_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
14:1.346
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.254
When I bump the system time with "+1 day" 0.294
And I capture all network traffic 0.003
And the network is plugged 9:2.242
And the Tor Connection Assistant autostarts 5.996
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 13.519
And I wait until Tor is ready 4:31.035
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:28:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:517 0.035
After features/support/hooks.rb:330 5.230 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:45:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:45:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.063
Feature: Time syncing
Tags: @product @check_tor_leaks
5:25.469
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.289
When I bump the system time with "+8 hours +15 minutes" 0.254
And all notifications have disappeared 4.122
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.091
And the network is plugged 0.087
And the Tor Connection Assistant autostarts 3.603
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.428
And I click "Connect to Tor" 1.170
And the Tor Connection Assistant fails to connect to Tor 15.799
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.920
Then the system clock is less than 20 minutes incorrect 0.322
When I click "Connect to Tor" 1.172
Then I wait until Tor is ready 4:30.203
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:77:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.039
After features/support/hooks.rb:330 5.295 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:55:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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_arti-1.4.3/12/artifact/build-artifacts/00:55:49_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.042
Feature: Time syncing
Tags: @product @check_tor_leaks
5:20.440
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.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.137
When I bump the system time with "+8 hours +15 minutes" 0.350
And all notifications have disappeared 4.081
And I capture all network traffic 0.003
And the network is plugged 0.082
And the Tor Connection Assistant autostarts 3.580
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.423
And I click "Connect to Tor" 1.185
Then the Tor Connection Assistant reports that it failed to connect 11.705
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.861
Then the system clock is less than 20 minutes incorrect 0.322
# "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.351
When I click "Connect to Tor" 1.155
Then I wait until Tor is ready 4:30.198
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:99:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:517 0.047
After features/support/hooks.rb:330 5.502 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 01:01:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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_arti-1.4.3/12/artifact/build-artifacts/01:01:15_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.031
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:44.165
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 13.110
Then I wait until Tor is ready 4:31.054
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:15:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.523 
SCENARIO FAILED: 'Using normal bridges' (at time 01:06:44)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:06:44_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.054
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.722
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 11.831
Then I wait until Tor is ready 4:31.890
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:22:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.679 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 01:11:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:11:46_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.054
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:2.680
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 30.798
Then I wait until Tor is ready 4:31.881
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:29:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.259 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 01:17:08)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:17:08_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.226
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.166
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.332
Then the Tor Connection Assistant reports that it failed to connect 0.112
And tca.conf is empty 0.245
Given I scan a QR code from the error page in Tor Connection Assistant 21.296
And I retry connecting to Tor 1.157
Then I wait until Tor is ready 4:30.915
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:41:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.316 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 01:22:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:22:54_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:45.038
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 14.086
Then I wait until Tor is ready 4:30.952
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:49:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.322 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:27:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:27:56_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.050
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.811
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.016
When I configure a direct connection in the Tor Connection Assistant 22.097
Then I wait until Tor is ready 4:30.696
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:59:in `Then I wait until Tor is ready'
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.507 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:33:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:33:09_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.051
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:57.728
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.035
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 22.778
Then the Tor Connection Assistant reports that it failed to connect 0.115
Given the Tor network and default bridges are unblocked 1.464
When I click "Connect to Tor" 1.149
Then I wait until Tor is ready 4:30.185
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:108:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.359 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:43:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/01:43:15_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.043
Feature: Upgrading an old Tails USB installation
Tags: @product
1:31.303
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.005
Steps
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.479
When I start Tails from USB drive "old" with network unplugged 58.542
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/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 4.797 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:42:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:42:33_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_arti-1.4.3/12/artifact/build-artifacts/02:42:33_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:42:33_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:42:33_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
42.375
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.005
Steps
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 42.202
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/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 4.749 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:43:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:43:20_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_arti-1.4.3/12/artifact/build-artifacts/02:43:20_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:43:20_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:43:20_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Feature: Upgrading an old Tails USB installation
Tags: @product
37.962
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.005
Steps
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 37.761
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/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 4.713 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:44:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:44:03_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_arti-1.4.3/12/artifact/build-artifacts/02:44:03_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_arti-1.4.3/12/artifact/build-artifacts/02:44:03_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_arti-1.4.3/12/artifact/build-artifacts/02:44:03_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
1:13.239
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.004
Steps
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.068
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:302: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 5.003 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:47:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:47:49_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_arti-1.4.3/12/artifact/build-artifacts/02:47:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:47:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/02:47:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.008
Feature: Packages are up-to-date
Tags: @source
15.211
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:534 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 15.211
Command 
Command failed (pid 60472 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/tmp/tails-amd64-arti-1.4.3@f5964b9c6f+stable@2afad972da-20250517T1921Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/tmp/tails-amd64-arti-1.4.3@f5964b9c6f+stable@2afad972da-20250517T1921Z.build-manifest
INFO: Need to upgrade our own forked package:
  - network-manager (1.42.4-1.0tails1) to Debian bookworm (1.42.4-1+deb12u1)
INFO: Need to upgrade to a new APT snapshot:
  - abseil (20220623.1-1) to Debian bookworm (20220623.1-1+deb12u2)
  - base-files (12.4+deb12u10) to Debian bookworm (12.4+deb12u11)
  - bash (5.2.15-2+b7) to Debian bookworm (5.2.15-2)
  - busybox (1:1.35.0-4+b3) to Debian bookworm (1:1.35.0-4)
  - debian-archive-keyring (2023.3+deb12u1) to Debian bookworm (2023.3+deb12u2)
  - distro-info-data (0.58+deb12u3) to Debian bookworm (0.58+deb12u4)
  - flatpak[flatpak] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[gir1.2-flatpak-1.0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[libflatpak0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - gcc-12[cpp-12] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[gcc-12-base, g++-12, gcc-12] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libatomic1, libasan8] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libcc1-0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libgcc-12-dev, libgcc-s1, libgfortran5] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libitm1, libgomp1, liblsan0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libobjc4] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libquadmath0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libtsan2, libubsan1, libstdc++6, libstdc++-12-dev] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - glib2.0 (2.74.6-2+deb12u5) to Debian bookworm (2.74.6-2+deb12u6)
  - imagemagick[imagemagick-6-common] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - imagemagick[libmagickcore-6.q16-6, libmagickwand-6.q16-6, libmagick++-6.q16-8] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - initramfs-tools (0.142+deb12u1) to Debian bookworm (0.142+deb12u3)
  - libcap2 (1:2.66-4) to Debian bookworm (1:2.66-4+deb12u1)
  - openssl[libssl3] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - openssl[openssl] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - poppler[gir1.2-poppler-0.18] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[libpoppler126, libpoppler-cpp0v5, libpoppler-glib8] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[poppler-utils] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - python3.11[libpython3.11-stdlib, libpython3.11-minimal, libpython3.11] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - python3.11[python3.11-minimal, python3.11] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - qtbase-opensource-src (5.15.8+dfsg-11+deb12u2) to Debian bookworm (5.15.8+dfsg-11+deb12u3)
  - shadow[login] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - shadow[passwd] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - tzdata (2025a-0+deb12u1) to Debian bookworm (2025b-0+deb12u1)
  - wireless-regdb (2022.06.06-1) to Debian bookworm (2025.02.20-1~deb12u1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/support/helpers/misc_helpers.rb:325:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/support/helpers/misc_helpers.rb:325:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_arti-1.4.3/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:541 0.000
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:25.234
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.111
And I create a persistent partition with the default settings 20.772
Then the "TorConfiguration" tps feature is not enabled 2.171
When the network is plugged 0.073
And the Tor Connection Assistant autostarts 8.619
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.015
And I wait until Tor is ready 4:30.468
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.615 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:55:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/04:55:57_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:21.468
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.475
And I create a persistent partition with the default settings 20.184
Then the "TorConfiguration" tps feature is not enabled 2.240
When the network is plugged 0.069
And the Tor Connection Assistant autostarts 6.897
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.069
And I wait until Tor is ready 4:30.530
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario 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.395 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:01:24)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:01:24_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:49.822
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.985
And a web server is running on the LAN 1.033
And I capture all network traffic 0.006
When I start the Tor Browser 24.957
And the Tor Browser loads the startup page 1.097
And I open a page on the LAN web server in the Tor Browser 11.741
Then the Tor Browser shows the "Unable to connect" error 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:334:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 7.576 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:21:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:21:53_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:21:53_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:21:53_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:21:53_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.053
Feature: Browsing the web using the Tor Browser
Tags: @product
1:8.857
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.046
When I start the Tor Browser 24.573
And the Tor Browser loads the startup page 1.090
Then Tor Browser's circuit view is working 32.146
The 
The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Tor Circuit" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:435:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:92:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 7.528 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:31:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:31:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:31:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:31:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/12/artifact/build-artifacts/05:31:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000