Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 9 11 Apr 2025, 15:42

Failures Overview

The following summary displays scenarios that failed.

26:53.541
Scenario Erasure of read and write disk caches of persistent data on shutdown
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 26:53.541
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:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 10.884

SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:02:11)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:02:11_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:02:11_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:02:11_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:100 0.009
Tags: @product @uefi
22:22.148
Scenario Booting Tails from a USB drive in UEFI mode
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 without a persistent partition and stopped at Tails Greeter's login screen 19.037
And I power off the computer 0.747
And the computer is set to boot in UEFI mode 0.127
When I start Tails from USB drive "__internal" with network unplugged and I login 22:2.235
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:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:330 10.897

SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:56:37)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:56:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:56:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/01:56:37_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal

After features/support/hooks.rb:100 0.006
2:27.623
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.613
And I prepare Tails for memory erasure tests 0.655
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 41.114
And I fill the USB drive with a known pattern 1.660
And I read the content of the test FS 0.086
And patterns cover at least 99% of the test FS size in the guest's memory 3.603

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

When I eject the boot medium 0.418
And I wait for Tails to finish wiping the memory 1:30.472
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232: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:330 10.875

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 02:57:32)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/02:57:32_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/02:57:32_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/02:57:32_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal

After features/support/hooks.rb:100 0.000
Tags: @product
36:40.454
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:40.434
And I update APT using apt 35:0.019
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:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/misc_helpers.rb:180:in `new'
./features/support/helpers/misc_helpers.rb:180:in `force_new_tor_circuit'
./features/support/helpers/misc_helpers.rb:192:in `block in retry_tor'
./features/support/helpers/misc_helpers.rb:222: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:59:in `/^I update APT using apt$/'
features/persistence.feature:8:in `And I update APT using apt'
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:330 10.767

SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 04:48:30)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/04:48:30_Tails_Persistent_Storage_behave_tests.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/04:48:30_Tails_Persistent_Storage_behave_tests.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/9/artifact/build-artifacts/04:48:30_Tails_Persistent_Storage_behave_tests.journal

After features/support/hooks.rb:100 0.000