Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 7 09 Jun 2025, 04:47

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 22:16.118 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:0.387
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.171
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.013
Then the computer boots Tails 52.060
And I see a disk failure message on the splash screen 7.143
After features/support/hooks.rb:330 0.616
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:1.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.012
Then the computer boots Tails 53.395
And I see a disk failure message on the splash screen 6.999
After features/support/hooks.rb:330 0.648
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:2.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.168
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.087
Then the computer boots Tails 54.256
And I see a disk failure message on the splash screen 6.638
After features/support/hooks.rb:330 0.587
After features/support/hooks.rb:100 0.006
Tags: @product @doc
19.894
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.163
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.731
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 0x70ec5fa4f7e0>
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.546 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:17:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_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/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_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/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
19.781
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.223
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.558
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 0x7720a6dff7e0>
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.129 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:18:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_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/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_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/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
19.635
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.172
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.463
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 0x7b5ed008f7e0>
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.850 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:18:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_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/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_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/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.289
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
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.685
And I corrupt the boot device's GPT backup header 0.373
And I power off the computer 0.364
When I start the computer 0.997
Then the computer boots Tails 1:47.659
When I log in to a new session 34.942
And all notifications have disappeared 12.988
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.278
<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.061 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 02:21:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_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/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_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/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.006
Tags: @product
2:48.014
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
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.936
And I corrupt the boot device's GPT backup partition table 0.396
And I power off the computer 0.336
When I start the computer 1.004
Then the computer boots Tails 1:50.053
When I log in to a new session 33.567
And all notifications have disappeared 13.487
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.233
<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.133 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:24:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_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/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_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/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.006
Tags: @product
4:8.444
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.168
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.039
And I plug USB drive "temp" 1.046
And I write the Tails USB image to disk "temp" 31.527
When I start Tails from USB drive "temp" with network unplugged 2:45.134
Then Tails is running from USB drive "temp" 0.398
And the Greeter forbids creating a persistent partition 0.086
When I log in to a new session 36.621
And all notifications have disappeared 13.128
Then I am recommended to reinstall Tails due to partitioning errors 0.289
<"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.104 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 02:28:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_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/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.118
Tags: @product
3:7.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.174
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.044
And I plug USB drive "temp" 1.048
And I write the Tails USB image to disk "temp" 28.938
When I start Tails from USB drive "temp" with network unplugged 2:36.497
Then Tails is running from USB drive "temp" 0.387
And the Greeter recommends reinstalling Tails due to partitioning errors 0.093
And the Greeter forbids starting Tails 0.068
And the Greeter forbids all settings but language 0.380
And Tails detected partitioning error guid-not-randomized 0.012
After features/support/hooks.rb:330 1.670
After features/support/hooks.rb:100 0.136
Tags: @product
2:47.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.171
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.043
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 27.505
When I start Tails from USB drive "temp" with network unplugged 2:17.391
Then Tails is running from USB drive "temp" 0.357
And the Greeter recommends reinstalling Tails due to partitioning errors 0.088
And the Greeter forbids starting Tails 0.097
And the Greeter forbids all settings but language 0.389
And Tails detected partitioning error system-partition-not-resized 0.012
After features/support/hooks.rb:330 1.450
After features/support/hooks.rb:100 0.143
Tags: @product
2:34.178
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.186
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.042
And I plug USB drive "temp" 1.120
And I write the Tails USB image to disk "temp" 26.915
When I start Tails from USB drive "temp" with network unplugged 2:5.033
Then Tails is running from USB drive "temp" 0.367
And the Greeter recommends reinstalling Tails due to partitioning errors 0.089
And the Greeter forbids starting Tails 0.075
And the Greeter forbids all settings but language 0.332
And Tails detected partitioning error fs-not-resized 0.013
After features/support/hooks.rb:330 0.916
After features/support/hooks.rb:100 0.161