Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 1 04 Jun 2025, 14:09

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 74 6 15 0 0 95 6 6 12 22:41.262 Failed
Tags: @product
Feature Hardware failures
In order to update my failing hardware before I lose data As a Tails user I want to be warned about hardware failures
Tags: @product @broken_welcome_screen
1:13.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.153
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.007
Then the computer boots Tails 54.437
And I see a disk failure message on the splash screen 17.407
After features/support/hooks.rb:330 2.842
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:10.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.167
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.164
Then the computer boots Tails 52.233
And I see a disk failure message on the splash screen 17.379
After features/support/hooks.rb:330 2.733
After features/support/hooks.rb:100 0.007
Tags: @product @broken_welcome_screen
1:10.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.153
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 1.008
Then the computer boots Tails 52.484
And I see a disk failure message on the splash screen 16.432
After features/support/hooks.rb:330 2.872
After features/support/hooks.rb:100 0.006
Tags: @product @doc
20.379
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.156
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.222
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x7b5d9d4a37e0>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'

 (RuntimeError)
./features/support/helpers/screen.rb:343:in `ponytail_press'
./features/support/helpers/screen.rb:351:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./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/hardware_failure.feature:29:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the SquashFS 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.077 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:19:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
20.276
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.161
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.115
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x799bf8d437e0>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'

 (RuntimeError)
./features/support/helpers/screen.rb:343:in `ponytail_press'
./features/support/helpers/screen.rb:351:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./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/hardware_failure.feature:30:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.159 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:19:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:33_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:33_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:33_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:33_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
19.983
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.184
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.799
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x7c22754877e0>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'

 (RuntimeError)
./features/support/helpers/screen.rb:343:in `ponytail_press'
./features/support/helpers/screen.rb:351:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./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/hardware_failure.feature:31:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device with a target error 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 5.991 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:19:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:19:59_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.307
Scenario Outline GPT backup corruption with a persistent partition
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 and stopped at Tails Greeter's login screen 9.018
And I corrupt the boot device's GPT backup header 0.481
And I power off the computer 0.329
When I start the computer 1.029
Then the computer boots Tails 1:54.779
When I log in to a new session 26.887
And all notifications have disappeared 3.783
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.AccessDenied: GetWindows is not allowed
STDOUT:

STDERR:

 (RuntimeError)
./features/support/helpers/screen.rb:343:in `ponytail_press'
./features/support/helpers/screen.rb:351:in `press'
./features/step_definitions/common_steps.rb:719:in `block (2 levels) in <top (required)>'
./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/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
features/hardware_failure.feature:45:in `And all notifications have disappeared'
features/hardware_failure.feature:40:in `And all notifications have disappeared'
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 5.711 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 02:22:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:22:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:22:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:22:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:22:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.007
Tags: @product
2:46.834
Scenario Outline GPT backup corruption with a persistent partition
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 and stopped at Tails Greeter's login screen 8.555
And I corrupt the boot device's GPT backup partition table 0.543
And I power off the computer 0.364
When I start the computer 1.011
Then the computer boots Tails 1:51.324
When I log in to a new session 29.608
And all notifications have disappeared 15.127
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.300
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.886 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:25:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:25:34_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:25:34_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:25:34_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:25:34_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.008
Tags: @product
3:54.405
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.190
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.033
And I plug USB drive "temp" 1.049
And I write the Tails USB image to disk "temp" 31.426
When I start Tails from USB drive "temp" with network unplugged 2:42.753
Then Tails is running from USB drive "temp" 0.416
And the Greeter forbids creating a persistent partition 0.103
When I log in to a new session 24.831
And all notifications have disappeared 13.381
Then I am recommended to reinstall Tails due to partitioning errors 0.218
<"OK"> 
<"OK"> was expected to include
<"Creation of Persistent Storage has been disabled">. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:94:in `/^I am recommended to reinstall Tails due to partitioning errors$/'
features/hardware_failure.feature:59:in `Then I am recommended to reinstall Tails due to partitioning errors'
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 0.000
And I am told that Persistent Storage cannot be created 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.271 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 02:29:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:29:35_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:29:35_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:29:35_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/1/artifact/build-artifacts/02:29:35_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.106
Tags: @product
3:19.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.158
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.048
And I plug USB drive "temp" 1.059
And I write the Tails USB image to disk "temp" 33.374
When I start Tails from USB drive "temp" with network unplugged 2:44.122
Then Tails is running from USB drive "temp" 0.379
And the Greeter recommends reinstalling Tails due to partitioning errors 0.094
And the Greeter forbids starting Tails 0.068
And the Greeter forbids all settings but language 0.350
And Tails detected partitioning error guid-not-randomized 0.012
After features/support/hooks.rb:330 1.664
After features/support/hooks.rb:100 0.141
Tags: @product
2:51.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.156
And I set Tails to boot with options "test_partitioning_errors=part_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.039
And I plug USB drive "temp" 1.049
And I write the Tails USB image to disk "temp" 28.703
When I start Tails from USB drive "temp" with network unplugged 2:20.231
Then Tails is running from USB drive "temp" 0.386
And the Greeter recommends reinstalling Tails due to partitioning errors 0.089
And the Greeter forbids starting Tails 0.067
And the Greeter forbids all settings but language 0.379
And Tails detected partitioning error system-partition-not-resized 0.013
After features/support/hooks.rb:330 1.499
After features/support/hooks.rb:100 0.152
Tags: @product
2:38.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.235
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.035
And I plug USB drive "temp" 1.047
And I write the Tails USB image to disk "temp" 27.897
When I start Tails from USB drive "temp" with network unplugged 2:8.110
Then Tails is running from USB drive "temp" 0.383
And the Greeter recommends reinstalling Tails due to partitioning errors 0.088
And the Greeter forbids starting Tails 0.063
And the Greeter forbids all settings but language 0.384
And Tails detected partitioning error fs-not-resized 0.011
After features/support/hooks.rb:330 2.214
After features/support/hooks.rb:100 0.190