Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 8 10 Jun 2025, 04:45

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 75 6 14 0 0 95 6 6 12 21:49.887 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:2.241
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.180
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.027
Then the computer boots Tails 54.605
And I see a disk failure message on the splash screen 6.428
After features/support/hooks.rb:330 0.582
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:2.289
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.192
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.016
Then the computer boots Tails 54.488
And I see a disk failure message on the splash screen 6.592
After features/support/hooks.rb:330 0.594
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:2.007
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.158
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.002
Then the computer boots Tails 53.609
And I see a disk failure message on the splash screen 7.238
After features/support/hooks.rb:330 0.666
After features/support/hooks.rb:100 0.006
Tags: @product @doc
21.698
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.308
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.389
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 0x779093a7f7e0>
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 5.796 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:15:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:15:18_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/8/artifact/build-artifacts/02:15:18_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:15:18_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/8/artifact/build-artifacts/02:15:18_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
20.147
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.170
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 0x7385f3e0f7e0>
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 5.519 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:15:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:15:44_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/8/artifact/build-artifacts/02:15:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:15:44_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/8/artifact/build-artifacts/02:15:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
21.752
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.216
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.536
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 0x7378d7c0f7e0>
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 5.934 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:16:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:16:11_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/8/artifact/build-artifacts/02:16:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:16:11_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/8/artifact/build-artifacts/02:16:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:50.260
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.029
And I corrupt the boot device's GPT backup header 0.615
And I power off the computer 0.332
When I start the computer 1.156
Then the computer boots Tails 1:49.212
When I log in to a new session 36.948
And all notifications have disappeared 12.689
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.276
<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:45: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.891 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 02:19:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:19:07_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/8/artifact/build-artifacts/02:19:07_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:19:07_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/8/artifact/build-artifacts/02:19:07_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.035
Tags: @product
2:48.689
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
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.941
And I corrupt the boot device's GPT backup partition table 0.495
And I power off the computer 0.329
When I start the computer 0.995
Then the computer boots Tails 1:47.280
When I log in to a new session 38.215
And all notifications have disappeared 12.171
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.259
<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.120 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:22:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:22:03_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/8/artifact/build-artifacts/02:22:03_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:22:03_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/8/artifact/build-artifacts/02:22:03_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.005
Tags: @product
3:42.983
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.177
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.055
And I plug USB drive "temp" 1.046
And I write the Tails USB image to disk "temp" 31.025
When I start Tails from USB drive "temp" with network unplugged 2:29.271
Then Tails is running from USB drive "temp" 0.357
And the Greeter forbids creating a persistent partition 0.105
When I log in to a new session 28.209
And all notifications have disappeared 12.477
Then I am recommended to reinstall Tails due to partitioning errors 0.256
<"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.634 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 02:25:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:25:52_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/8/artifact/build-artifacts/02:25:52_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:25:52_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/8/artifact/build-artifacts/02:25:52_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.093
Tags: @product
2:52.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.168
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.047
And I plug USB drive "temp" 1.065
And I write the Tails USB image to disk "temp" 31.442
When I start Tails from USB drive "temp" with network unplugged 2:18.522
Then Tails is running from USB drive "temp" 0.380
And the Greeter recommends reinstalling Tails due to partitioning errors 0.091
And the Greeter forbids starting Tails 0.064
And the Greeter forbids all settings but language 0.366
And Tails detected partitioning error guid-not-randomized 0.012
After features/support/hooks.rb:330 1.637
After features/support/hooks.rb:100 0.151
Tags: @product
2:52.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.170
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.047
And I plug USB drive "temp" 1.047
And I write the Tails USB image to disk "temp" 27.215
When I start Tails from USB drive "temp" with network unplugged 2:23.419
Then Tails is running from USB drive "temp" 0.390
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.064
And the Greeter forbids all settings but language 0.359
And Tails detected partitioning error system-partition-not-resized 0.015
After features/support/hooks.rb:330 1.607
After features/support/hooks.rb:100 0.177
Tags: @product
2:32.832
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.175
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.038
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 27.233
When I start Tails from USB drive "temp" with network unplugged 2:3.315
Then Tails is running from USB drive "temp" 0.440
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.071
And the Greeter forbids all settings but language 0.398
And Tails detected partitioning error fs-not-resized 0.014
After features/support/hooks.rb:330 1.477
After features/support/hooks.rb:100 0.167