Cucumber Reports (no 8) - Failures Overview

Project	Number	Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix	8	29 Oct 2024, 02:43

Feature: Additional software

8:8.893

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

Given a computer 0.222

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:21.561

And I configure APT to prefer an old version of cowsay 0.025

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 28.785

And I accept adding "cowsay" to Additional Software 5.330

And Additional Software is correctly configured for package "cowsay" 1.122

And I shutdown Tails and wait for the computer to power off 6.945

And I start Tails from USB drive "__internal" with network unplugged 58.980

And I enable persistence 11.855

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.026

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.106

And I log in to a new session 38.327

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:13.871

And I revert the APT tweaks that made it prefer an old version of cowsay 0.056

# We remove the newest package after it has been downloaded and before

# it is installed, so that the upgrade process fails

And I prepare the Additional Software upgrade process to fail 0.068

And the network is plugged 0.069

And Tor is ready 1:1.538

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
features/additional_software_packages.feature:100:in `And Tor is ready'

And available upgrades have been checked 0.000

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000

And I can open the Additional Software configuration window from the notification 0.000

And I shutdown Tails and wait for the computer to power off 0.000

And I start Tails from USB drive "__internal" with network unplugged 0.000

And I enable persistence 0.000

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.000

And I log in to a new session 0.000

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000

And I revert the APT tweaks that made it prefer an old version of cowsay 0.000

And the network is plugged 0.000

And Tor is ready 0.000

Then the Additional Software upgrade service has started 0.000

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000

Hooks

After features/support/hooks.rb:515 0.037

After features/support/hooks.rb:326 14.200

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:27:28)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/01:27:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/01:27:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/01:27:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/01:27:28_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.016

Feature: Hardware failures

Tags: @product

36.406

Scenario Outline Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.198

And I start the computer from DVD with network unplugged 36.130

When Tails detects disk read failures on the SquashFS 0.077

Command

Command failed: systemctl --quiet is-active tails-detect-disk-ioerrors
error code: 3
stdout: 
stderr: .
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:483:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:480:in `execute_successfully'
./features/step_definitions/hardware.rb:33:in `/^Tails detects disk read failures on the (.+)$/'
features/hardware_failure.feature:14:in `When Tails detects disk read failures on the SquashFS'
features/hardware_failure.feature:10:in `When Tails detects disk read failures on the <device>'

Then I see a disk failure message on the splash screen 0.000

Hooks

After features/support/hooks.rb:326 4.760

Output 1

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#1)' (at time 02:08:38)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/02:08:38_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_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/02:08:38_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.journal

After features/support/hooks.rb:100 0.009

Feature: Tails persistence

Tags: @product

2:9.862

Scenario LUKS backup header is restored if something goes wrong during upgrade

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 9.101

And I enable persistence but something goes wrong during the LUKS header upgrade 2:0.760

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:712:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'

Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000

Hooks

After features/support/hooks.rb:326 4.988

Output 1

SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:34:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/03:34:49_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/03:34:49_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/03:34:49_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/8/artifact/build-artifacts/03:34:49_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal

After features/support/hooks.rb:100 0.000