Cucumber Reports (no 4715) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4715	13 Mar 2024, 15:32

Feature: Hardware failures

Tags: @product

5:13.915

Scenario Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:245 0.006

Steps

Given a computer 0.211

And I start the computer from DVD with network unplugged 5:13.704

Remote

Remote shell seems to be down (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/support/helpers/vm_helper.rb:509:in `wait_until_remote_shell_is_up'
./features/step_definitions/common_steps.rb:443:in `the_computer_boots'
./features/step_definitions/hardware.rb:10:in `/^I start the computer from DVD with network unplugged( and an unsupported graphics card)?$/'
features/hardware_failure.feature:9:in `And I start the computer from DVD with network unplugged'

When Tails detects disk read failures 0.000

Then I see a disk failure message on the splash screen 0.000

Hooks

After features/support/hooks.rb:291 4.429

Output 1

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen' (at time 02:06:46)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4715/artifact/build-artifacts/02:06:46_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4715/artifact/build-artifacts/02:06:46_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4715/artifact/build-artifacts/02:06:46_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4715/artifact/build-artifacts/02:06:46_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen.journal

After features/support/hooks.rb:75 0.009

Feature: Using persistent Tor bridges and pluggable transports

4:5.452

Background

Hooks

Before features/support/hooks.rb:245 0.004

Steps

Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.008

And I create a persistent partition with the default settings 30.346

Then the "TorConfiguration" tps feature is not enabled 1.030

When the network is plugged 0.037

And the Tor Connection Assistant autostarts 6.203

And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.832

And I wait until Tor is ready 3.125

Then tca.conf includes the configured bridges 0.020

And the "TorConfiguration" tps feature is enabled and active 0.863

When I cold reboot the computer 9.089

And the computer reboots Tails 54.925

And I enable persistence 22.535

And I capture all network traffic 0.006

And I log in to a new session 36.384

Then tca.conf includes the configured bridges 0.012

When the network is plugged 0.029

And the Tor Connection Assistant autostarts 1:0.001

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:360:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:356:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
features/persistent_tor_bridges.feature:24:in `And the Tor Connection Assistant autostarts'

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

Hooks

After features/support/hooks.rb:291 20:3.521

Error message

execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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:124:in `execute'
./features/support/helpers/remote_shell.rb:135:in `initialize'
./features/support/helpers/vm_helper.rb:445:in `new'
./features/support/helpers/vm_helper.rb:445:in `execute'
./features/support/helpers/misc_helpers.rb:245:in `block in save_tor_journal'
./features/support/helpers/misc_helpers.rb:244:in `open'
./features/support/helpers/misc_helpers.rb:244:in `save_tor_journal'
./features/support/hooks.rb:328:in `After'

Output 1

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 03:35:42)

After features/support/hooks.rb:75 0.056