Project Number Date
test_Tails_ISO_stable 4848 19 May 2024, 12:45

Failures Overview

The following summary displays scenarios that failed.

2:22.161
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.460
And I prepare Tails for memory erasure tests 0.503
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 36.687
And I fill the USB drive with a known pattern 1.422
And I read the content of the test FS 0.067
And patterns cover at least 99% of the test FS size in the guest's memory 3.238

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

When I eject the boot medium 1.770
And I wait for Tails to finish wiping the memory 1:30.010
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/erase_memory.rb:229:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:305 9.481

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:53:46)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/01:53:46_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/01:53:46_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

After features/support/hooks.rb:89 0.000
Tags: @product
20.920
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.032
Then the keys trusted by APT are valid for the next 3 months 12.887
The
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29: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:305 4.371

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:12:42)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/02:12:42_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/02:12:42_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/02:12:42_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4848/artifact/build-artifacts/02:12:42_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000