Project Number Date
test_Tails_ISO_stable 5987 06 Dec 2025, 21:07

Failures Overview

The following summary displays scenarios that failed.

Feature: Packages are up-to-date
Tags: @source
3.873
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:544 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 3.873
Command 
Command failed (pid 45206 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@c9c52799f6-20251206T1350Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@c9c52799f6-20251206T1350Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2025-12-06 18:05:02+00:00 (1:32:03.489363 ago)
WARNING: tor-geoipdb: the package version (0.4.8.21-1~d13.trixie+1) is higher than the newest version in Debian (0.4.8.16-1)
WARNING: tor: the package version (0.4.8.21-1~d13.trixie+1) is higher than the newest version in Debian (0.4.8.16-1)
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20251021-1) to Debian forky (20251111-1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:551 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:10.692
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.567
Then Tails is running from USB drive "__internal" 0.354
When I create a file in the Persistent directory 0.134
And I create a persistent partition with the default settings 49.634
Then the file I created was copied to the Persistent Storage 10.001
The 
The file /live/persistence/TailsData_unlocked/Persistent/foo does not exist after 10 seconds (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:949:in `/^the file "([^"]+)" exists(?:| after at most (\d+) seconds)$/'
./features/step_definitions/usb.rb:1670:in `/^the file I created was copied to the Persistent Storage$/'
features/persistence.feature:24:in `Then the file I created was copied to the Persistent Storage'
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:331 14.823 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 02:37:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:37:02_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:37:02_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:37:02_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
29.911
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.661
Then Tails is running from USB drive "__internal" 0.529
And all tps features are active 2.333
And all persistent directories have safe access rights 2.513
When I disable the first tps feature 13.874
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/usb.rb:307:in `/^I (enable|disable) the first tps feature$/'
features/persistence.feature:46:in `When I disable the first tps feature'
Then all tps features but the first one are active 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:331 7.588 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 02:39:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:39:10_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:39:10_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:39:10_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/02:39:10_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
41.529
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 25.783
And I cancel the GNOME authentication prompt 1.913
And I unlock and mount this VeraCrypt volume with GNOME Disks 9.618
And I open this VeraCrypt volume in GNOME Files 2.467
Then I see the expected contents in this VeraCrypt volume 0.205
When I lock the currently opened VeraCrypt volume 1.379
Then the VeraCrypt volume has been unmounted and locked 0.161
<["/dev/mapper/tcrypt-2048"]> 
<["/dev/mapper/tcrypt-2048"]> was expected to be empty. (Test::Unit::AssertionFailedError)
./features/step_definitions/veracrypt.rb:337:in `/^the VeraCrypt (?:volume|file container) has been unmounted and locked$/'
features/veracrypt.feature:64:in `Then the VeraCrypt volume has been unmounted and locked'
After features/support/hooks.rb:331 11.501 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 03:51:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/03:51:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/03:51:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/03:51:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5987/artifact/build-artifacts/03:51:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000