Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 11 14 Jun 2025, 04:38

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 83 3 9 0 0 95 9 3 12 21:45.965 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:5.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.202
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.055
Then the computer boots Tails 56.421
And I see a disk failure message on the splash screen 7.848
After features/support/hooks.rb:330 0.650
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
59.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.148
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.995
Then the computer boots Tails 54.830
And I see a disk failure message on the splash screen 3.057
After features/support/hooks.rb:330 0.659
After features/support/hooks.rb:100 0.026
Tags: @product @broken_welcome_screen
1:1.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.165
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.016
Then the computer boots Tails 53.442
And I see a disk failure message on the splash screen 6.541
After features/support/hooks.rb:330 0.571
After features/support/hooks.rb:100 0.006
Tags: @product @doc
20.043
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.151
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.891
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 0x78d10b8437e0>
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:344:in `ponytail_press'
./features/support/helpers/screen.rb:352: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.365 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:13:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:13:56_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/11/artifact/build-artifacts/02:13:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:13:56_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/11/artifact/build-artifacts/02:13:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
19.942
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.153
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.789
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 0x7a33daca77e0>
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:344:in `ponytail_press'
./features/support/helpers/screen.rb:352: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.315 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:14:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:14:22_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/11/artifact/build-artifacts/02:14:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:14:22_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/11/artifact/build-artifacts/02:14:22_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
20.130
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.154
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.976
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 0x7c38e4e237e0>
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:344:in `ponytail_press'
./features/support/helpers/screen.rb:352: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 6.283 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:14:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:14:49_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/11/artifact/build-artifacts/02:14:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/11/artifact/build-artifacts/02:14:49_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/11/artifact/build-artifacts/02:14:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.046
And I corrupt the boot device's GPT backup header 0.530
And I power off the computer 0.336
When I start the computer 1.025
Then the computer boots Tails 1:49.690
When I log in to a new session 31.869
And all notifications have disappeared 12.229
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.251
And Tails detected partitioning error partitioning-corruption 0.012
After features/support/hooks.rb:330 1.900
After features/support/hooks.rb:100 0.006
Tags: @product
2:46.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.003
And I corrupt the boot device's GPT backup partition table 0.549
And I power off the computer 0.333
When I start the computer 1.054
Then the computer boots Tails 1:46.040
When I log in to a new session 36.126
And all notifications have disappeared 12.767
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.221
And Tails detected partitioning error partitioning-corruption 0.015
After features/support/hooks.rb:330 1.949
After features/support/hooks.rb:100 0.006
Tags: @product
3:51.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.154
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.037
And I plug USB drive "temp" 1.048
And I write the Tails USB image to disk "temp" 33.423
When I start Tails from USB drive "temp" with network unplugged 2:23.119
Then Tails is running from USB drive "temp" 0.403
And the Greeter forbids creating a persistent partition 0.085
When I log in to a new session 35.040
And all notifications have disappeared 13.021
Then I am recommended to reinstall Tails due to partitioning errors 0.211
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 1.347
And I am told that Persistent Storage cannot be created 3.092
And Tails detected partitioning error partitioning-corruption 0.022
After features/support/hooks.rb:330 2.163
After features/support/hooks.rb:100 0.139
Tags: @product
2:55.208
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
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.035
And I plug USB drive "temp" 1.045
And I write the Tails USB image to disk "temp" 32.714
When I start Tails from USB drive "temp" with network unplugged 2:20.324
Then Tails is running from USB drive "temp" 0.402
And the Greeter recommends reinstalling Tails due to partitioning errors 0.080
And the Greeter forbids starting Tails 0.094
And the Greeter forbids all settings but language 0.337
And Tails detected partitioning error guid-not-randomized 0.011
After features/support/hooks.rb:330 1.662
After features/support/hooks.rb:100 0.142
Tags: @product
2:46.685
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.233
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.038
And I plug USB drive "temp" 1.045
And I write the Tails USB image to disk "temp" 29.107
When I start Tails from USB drive "temp" with network unplugged 2:15.141
Then Tails is running from USB drive "temp" 0.569
And the Greeter recommends reinstalling Tails due to partitioning errors 0.117
And the Greeter forbids starting Tails 0.065
And the Greeter forbids all settings but language 0.353
And Tails detected partitioning error system-partition-not-resized 0.013
After features/support/hooks.rb:330 1.725
After features/support/hooks.rb:100 0.172
Tags: @product
2:36.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
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.039
And I plug USB drive "temp" 1.047
And I write the Tails USB image to disk "temp" 28.098
When I start Tails from USB drive "temp" with network unplugged 2:5.827
Then Tails is running from USB drive "temp" 0.455
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.066
And the Greeter forbids all settings but language 0.316
And Tails detected partitioning error fs-not-resized 0.013
After features/support/hooks.rb:330 1.487
After features/support/hooks.rb:100 0.155