Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 9 11 Jun 2025, 04:53

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:41.079 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:1.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.167
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.006
Then the computer boots Tails 53.715
And I see a disk failure message on the splash screen 6.442
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:0.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.162
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.980
Then the computer boots Tails 52.775
And I see a disk failure message on the splash screen 6.539
After features/support/hooks.rb:330 0.632
After features/support/hooks.rb:100 0.006
Tags: @product @broken_welcome_screen
1:0.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.163
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.006
Then the computer boots Tails 52.663
And I see a disk failure message on the splash screen 6.268
After features/support/hooks.rb:330 0.596
After features/support/hooks.rb:100 0.020
Tags: @product @doc
19.829
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.169
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.659
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 0x7ed0851737e0>
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.521 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:15:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:15:10_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/9/artifact/build-artifacts/02:15:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:15:10_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/9/artifact/build-artifacts/02:15:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
20.271
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.165
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.106
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 0x7ad3b310b7e0>
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.341 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:15:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:15:36_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/9/artifact/build-artifacts/02:15:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:15:36_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/9/artifact/build-artifacts/02:15:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Tags: @product @doc
20.710
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.185
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.525
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 0x78f9123237e0>
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.668 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:16:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:16:03_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/9/artifact/build-artifacts/02:16:03_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:16:03_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/9/artifact/build-artifacts/02:16:03_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.934
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.800
And I corrupt the boot device's GPT backup header 0.355
And I power off the computer 0.340
When I start the computer 1.018
Then the computer boots Tails 1:44.659
When I log in to a new session 34.528
And all notifications have disappeared 12.000
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.231
<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.565 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 02:18:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:18:51_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/9/artifact/build-artifacts/02:18:51_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:18:51_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/9/artifact/build-artifacts/02:18:51_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.006
Tags: @product
2:42.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.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.608
And I corrupt the boot device's GPT backup partition table 0.404
And I power off the computer 0.335
When I start the computer 1.025
Then the computer boots Tails 1:45.306
When I log in to a new session 34.168
And all notifications have disappeared 12.187
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.252
<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.592 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:21:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:21:39_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/9/artifact/build-artifacts/02:21:39_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:21:39_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/9/artifact/build-artifacts/02:21:39_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.005
Tags: @product
4:3.503
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.184
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.057
And I plug USB drive "temp" 1.047
And I write the Tails USB image to disk "temp" 29.901
When I start Tails from USB drive "temp" with network unplugged 2:44.672
Then Tails is running from USB drive "temp" 0.368
And the Greeter forbids creating a persistent partition 0.094
When I log in to a new session 33.308
And all notifications have disappeared 13.591
Then I am recommended to reinstall Tails due to partitioning errors 0.278
<"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.378 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 02:25:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:25:50_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/9/artifact/build-artifacts/02:25:50_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:25:50_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/9/artifact/build-artifacts/02:25:50_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.097
Tags: @product
2:57.194
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.041
And I plug USB drive "temp" 1.045
And I write the Tails USB image to disk "temp" 30.348
When I start Tails from USB drive "temp" with network unplugged 2:24.673
Then Tails is running from USB drive "temp" 0.385
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.355
And Tails detected partitioning error guid-not-randomized 0.013
After features/support/hooks.rb:330 7.265
After features/support/hooks.rb:100 0.131
Tags: @product
2:45.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.169
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.041
And I plug USB drive "temp" 1.053
And I write the Tails USB image to disk "temp" 27.508
When I start Tails from USB drive "temp" with network unplugged 2:16.215
Then Tails is running from USB drive "temp" 0.354
And the Greeter recommends reinstalling Tails due to partitioning errors 0.098
And the Greeter forbids starting Tails 0.095
And the Greeter forbids all settings but language 0.354
And Tails detected partitioning error system-partition-not-resized 0.012
After features/support/hooks.rb:330 1.719
After features/support/hooks.rb:100 0.144
Tags: @product
2:27.548
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.176
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.041
And I plug USB drive "temp" 1.047
And I write the Tails USB image to disk "temp" 26.155
When I start Tails from USB drive "temp" with network unplugged 1:59.228
Then Tails is running from USB drive "temp" 0.368
And the Greeter recommends reinstalling Tails due to partitioning errors 0.084
And the Greeter forbids starting Tails 0.067
And the Greeter forbids all settings but language 0.365
And Tails detected partitioning error fs-not-resized 0.013
After features/support/hooks.rb:330 1.427
After features/support/hooks.rb:100 0.152