Cucumber Reports (no 4939) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4939	14 Jul 2024, 12:10

Feature: Time syncing

1:53.947

Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.002

Steps

Given I have started Tails from DVD without network and logged in 29.549

When I bump the system time with "+8 hours +15 minutes" 0.420

And all notifications have disappeared 4.095

And I capture all network traffic 0.002

And I make sure time sync before Tor connects fails 0.135

And the network is plugged 0.042

And the Tor Connection Assistant autostarts 3.413

When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 6.216

And I click "Connect to Tor" 1.179

And the Tor Connection Assistant fails to connect to Tor 15.732

# The "Fix Clock" button allows users to recover from this bug

Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.686

Then the system clock is less than 20 minutes incorrect 0.290

When I click "Connect to Tor" 1.145

Then I wait until Tor is ready 37.037

The

The system is not fully running yet:
No jobs running.

  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 (RuntimeError)
./features/step_definitions/common_steps.rb:680:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:675: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

Hooks

After features/support/hooks.rb:515 0.031

After features/support/hooks.rb:326 4.842

Output 1

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:18:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:18:32_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_stable/4939/artifact/build-artifacts/00:18:32_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:18:32_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_stable/4939/artifact/build-artifacts/00:18:32_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.035

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

27.321

Scenario Erasure of read and write disk caches on unmount: vfat

Hooks

Before features/support/hooks.rb:269 0.002

Steps

Given I have started Tails from DVD without network and logged in 8.031

And I prepare Tails for memory erasure tests 0.418

When I plug and mount a 128 MiB USB drive with a vfat filesystem 8.906

Then I find very few patterns in the guest's memory 4.197

Output 1

Pattern coverage: 0.000% (0 MiB out of 906 MiB reference memory)

# write cache

When I fill the USB drive with a known pattern 2.528

Then patterns cover at least 86% of the test FS size in the guest's memory 3.239

85.777%

85.777% of the test FS size (127.599609375 MiB) has the pattern, but more than 86.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/erase_memory.feature:37:in `Then patterns cover at least 86% of the test FS size in the guest's memory'

Output 1

Pattern coverage: 85.777% (109 MiB out of 127 MiB reference memory)

When I umount the USB drive 0.000

Then I find very few patterns in the guest's memory 0.000

# read cache

When I mount the USB drive again 0.000

And I read the content of the test FS 0.000

Then patterns cover at least 99% of the test FS size in the guest's memory 0.000

When I umount the USB drive 0.000

Then I find very few patterns in the guest's memory 0.000

Hooks

After features/support/hooks.rb:326 4.923

Output 1

SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: vfat' (at time 00:30:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:30:29_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:30:29_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:30:29_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4939/artifact/build-artifacts/00:30:29_Erasure_of_read_and_write_disk_caches_on_unmount:_vfat.journal

After features/support/hooks.rb:100 0.000