Project Number Date
test_Tails_ISO_tps-restart-gnome-software 2 11 Jun 2026, 13:39

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
1:28.823
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.026
Steps
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 58.742
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 25.296
And I take note of which tps features are available 4.316
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 5.149

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:12:04_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:108 0.031
Tags: @product
1:16.930
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.038
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.227
Then Tails is running from USB drive "old" 0.326
And all tps features are active 5.064
When I write some files expected to persist 0.130
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.029

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:13:26_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:108 0.023
Tags: @product
1:15.570
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.019
Steps
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.496
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.562
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.796

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_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_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:17:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:108 0.018
Tags: @product
1:14.252
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Steps
Given a computer 0.185
And I set Tails to boot with options "test_partitioning_errors=guid" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.039
And I plug USB drive "temp" 1.040
And I write the Tails USB image to disk "temp" 14.418
When I start Tails from USB drive "temp" with network unplugged 58.569
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:447:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235: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/hardware_failure.feature:80:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error guid-not-randomized 0.000
After features/support/hooks.rb:339 5.365

SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#1)' (at time 01:44:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:44:05_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:44:05_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:44:05_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tps-restart-gnome-software/2/artifact/build-artifacts/01:44:05_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:108 0.144