Project Number Date
test_Tails_ISO_devel 4443 11 Jun 2026, 15:00

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
1:27.651
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Steps
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 57.465
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.412
And I take note of which tps features are available 4.332
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1124:in `/^I take note of which tps features are available$/'
features/usb_upgrade.feature:39:in `And I take note of which tps features are available'
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:339 4.948

SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:14:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:14:48_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:108 0.024
Tags: @product
1:17.585
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Steps
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.465
Then Tails is running from USB drive "old" 0.298
And all tps features are active 5.463
When I write some files expected to persist 0.149
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1083:in `/^I write some files expected to persist$/'
features/usb_upgrade.feature:49:in `When I write some files expected to persist'
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:339 5.025

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:16:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:16:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:16:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:16:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:16:10_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:108 0.057
Tags: @product
1:19.470
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Steps
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.241
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.623
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:1132:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 4.938

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:19:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4443/artifact/build-artifacts/01:19:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:108 0.023
2.421
Scenario All packages are up-to-date
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:552 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 2.420
Command failed (pid 130275 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@dd20d685c8-20260611T1017Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@dd20d685c8-20260611T1017Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-06-11 12:05:02+00:00 (1:17:56.129980 ago)
WARNING: tor-geoipdb: the package version (0.4.9.9-1~d13.trixie+1) is higher than the newest version in Debian (0.4.9.8-1)
WARNING: tor: the package version (0.4.9.9-1~d13.trixie+1) is higher than the newest version in Debian (0.4.9.8-1)
INFO: Need to upgrade to a new APT snapshot:
  - libinput (1.28.1-1) to Debian trixie-security (1.28.1-1+deb13u1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/step_definitions/needed_package_updates.rb:10:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:13:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:559 0.000
After features/support/hooks.rb:108 0.000