Project Number Date
test_Tails_ISO_improved-new-identity-scenario 7 06 May 2025, 13:56

Failures Overview

The following summary displays scenarios that failed.

Feature: Emergency shutdown
Tags: @product @not_release_blocker
55.325
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.007
Steps
Given I have started Tails from DVD without network and logged in 8.839
And I prepare Tails for memory erasure tests 0.537
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 45.949
try_for() 
try_for() timeout expired (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/common_steps.rb:791:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1500:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/emergency_shutdown.feature:39:in `And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
And I fill the USB drive with a known pattern 0.000
And I read the content of the test FS 0.000
And patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 7.499 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 02:04:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/02:04:52_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/02:04:52_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/02:04:52_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/02:04:52_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.005
Feature: Packages are up-to-date
Tags: @source
1:3.336
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:536 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 1:3.336
Command 
Command failed (returned pid 58105 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/tmp/tails-amd64-improved-new-identity-scenario@2ca4dbdc6d+stable@8494612b68-20250506T0751Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/tmp/tails-amd64-improved-new-identity-scenario@2ca4dbdc6d+stable@8494612b68-20250506T0751Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20241210-1) to Debian trixie (20241210-2)
  - firmware-nonfree[firmware-intel-graphics, firmware-brcm80211, firmware-intel-sound, firmware-atheros, firmware-iwlwifi, firmware-amd-graphics, firmware-ipw2x00, firmware-libertas, firmware-intel-misc] (20241210-1) to Debian trixie (20250410-2)
  - firmware-nonfree[firmware-nvidia-graphics, firmware-linux-nonfree, firmware-ti-connectivity, firmware-mediatek, firmware-misc-nonfree, firmware-realtek, firmware-linux] (20241210-1) to Debian trixie (20250410-2)
.
<0> expected but was
<#<Process::Status: pid 58105 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_improved-new-identity-scenario/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:543 0.000
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
33.019
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.368
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 16.650
try_for() 
try_for() timeout expired (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/veracrypt.rb:190:in `/^I unlock and mount this VeraCrypt (volume|file container) with Unlock VeraCrypt Volumes$/'
features/veracrypt.feature:32:in `And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 7.005 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 05:23:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/05:23:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/05:23:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/05:23:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/7/artifact/build-artifacts/05:23:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000