Project Number Date
test_Tails_ISO_feature-arti 1 24 Jun 2026, 19:52

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Hardware failures 32 12 51 0 0 95 0 12 12 8:47.680 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
23.752
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.066
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 0.866
Then the computer boots Tails 22.818
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d8ce48> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
features/hardware_failure.feature:16:in `Then the computer boots Tails'
features/hardware_failure.feature:12:in `Then the computer boots Tails'
And I see a disk failure message on the splash screen 0.000
After features/support/hooks.rb:339 5.011 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#1)' (at time 00:45:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:45:40_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:45:40_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:45:40_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:45:40_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.journal
After features/support/hooks.rb:108 0.006
Tags: @product @broken_welcome_screen
23.736
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.061
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 0.851
Then the computer boots Tails 22.822
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d77a98> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
features/hardware_failure.feature:17:in `Then the computer boots Tails'
features/hardware_failure.feature:12:in `Then the computer boots Tails'
And I see a disk failure message on the splash screen 0.000
After features/support/hooks.rb:339 4.988 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 00:46:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:09_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:09_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:09_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:09_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal
After features/support/hooks.rb:108 0.005
Tags: @product @broken_welcome_screen
23.015
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.051
And boot device with a target error is damaged in a way that some read operations fail 0.000
When I start the computer 0.741
Then the computer boots Tails 22.223
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d7f8d8> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
features/hardware_failure.feature:18:in `Then the computer boots Tails'
features/hardware_failure.feature:12:in `Then the computer boots Tails'
And I see a disk failure message on the splash screen 0.000
After features/support/hooks.rb:339 4.845 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#3)' (at time 00:46:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:37_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:37_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:37_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:46:37_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___3_.journal
After features/support/hooks.rb:108 0.005
Tags: @product @doc
55.722
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.059
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 55.662
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d77458> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226: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:339 5.117 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 00:47:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:47:38_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_feature-arti/1/artifact/build-artifacts/00:47:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:47:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:47:38_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:108 0.006
Tags: @product @doc
45.242
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.075
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 45.166
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d7f3d8> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226: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:339 4.990 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 00:48:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:48:28_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_feature-arti/1/artifact/build-artifacts/00:48:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:48:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:48:28_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:108 0.005
Tags: @product @doc
53.857
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.054
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 53.803
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d7fb58> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226: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:339 4.913 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 00:49:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:49:27_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_feature-arti/1/artifact/build-artifacts/00:49:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:49:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:49:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:108 0.033
Tags: @product
53.834
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 53.834
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d75518> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/hardware_failure.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
features/hardware_failure.feature:34:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And I corrupt the boot device's GPT backup header 0.000
And I power off the computer 0.000
When I start the computer 0.000
Then the computer boots Tails 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
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:339 4.944 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 00:50:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:50:26_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_feature-arti/1/artifact/build-artifacts/00:50:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:50:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:50:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:108 0.006
Tags: @product
49.910
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 49.910
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d7f518> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/hardware_failure.feature:46:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
features/hardware_failure.feature:34:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And I corrupt the boot device's GPT backup partition table 0.000
And I power off the computer 0.000
When I start the computer 0.000
Then the computer boots Tails 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
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:339 4.925 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 00:51:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:51:21_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_feature-arti/1/artifact/build-artifacts/00:51:21_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:51:21_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:51:21_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:108 0.015
Tags: @product
55.034
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.065
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.007
And I plug USB drive "temp" 1.016
And I write the Tails USB image to disk "temp" 13.045
When I start Tails from USB drive "temp" with network unplugged 40.899
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d71418> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/hardware_failure.feature:54:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter forbids creating a persistent partition 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then I am recommended to reinstall Tails due to partitioning errors 0.000
# 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:339 4.708 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 00:52:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:52:20_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:52:20_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:52:20_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:52:20_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:108 0.113
Tags: @product
48.951
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.055
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.007
And I plug USB drive "temp" 1.014
And I write the Tails USB image to disk "temp" 12.972
When I start Tails from USB drive "temp" with network unplugged 34.902
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d7fc98> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/hardware_failure.feature:80:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error guid-not-randomized 0.000
After features/support/hooks.rb:339 4.834 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#1)' (at time 00:53:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:53:14_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:53:14_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:53:14_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:53:14_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:108 0.105
Tags: @product
47.780
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.068
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.011
And I plug USB drive "temp" 1.024
And I write the Tails USB image to disk "temp" 13.132
When I start Tails from USB drive "temp" with network unplugged 33.544
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d8fdc8> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/hardware_failure.feature:81:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error system-partition-not-resized 0.000
After features/support/hooks.rb:339 4.964 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#2)' (at time 00:54:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:07_Disk_partitioning_errors_without_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:07_Disk_partitioning_errors_without_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:07_Disk_partitioning_errors_without_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:07_Disk_partitioning_errors_without_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:108 0.105
Tags: @product
46.840
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given a computer 0.062
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.012
And I plug USB drive "temp" 1.019
And I write the Tails USB image to disk "temp" 13.808
When I start Tails from USB drive "temp" with network unplugged 31.937
undefined 
undefined local variable or method `chutney_env' for #<Object:0x00007eff37d8f8c8> (NameError)
./features/step_definitions/chutney.rb:303:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:427:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:249:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/hardware_failure.feature:82:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error fs-not-resized 0.000
After features/support/hooks.rb:339 4.942 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 00:54:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:59_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:59_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:59_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/1/artifact/build-artifacts/00:54:59_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal
After features/support/hooks.rb:108 0.111