Project Number Date
test_Tails_ISO_stable 5455 12 Feb 2025, 21:01

Failures Overview

The following summary displays scenarios that failed.

6:52.238
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.013
Before features/support/hooks.rb:507 0.014
Steps
Given a computer 0.694
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:24.642
And I configure APT to prefer an old version of cowsay 0.034
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.552
And I accept adding "cowsay" to Additional Software 7.483
And Additional Software is correctly configured for package "cowsay" 0.927
And I shutdown Tails and wait for the computer to power off 7.019
And I start Tails from USB drive "__internal" with network unplugged 1:9.860
And I enable persistence 12.608
# 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.031
# 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.085
And I log in to a new session 40.914
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.280
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.084
And the network is plugged 0.062
And Tor is ready 48.348
And available upgrades have been checked 0.058
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.654
And I can open the Additional Software configuration window from the notification 10.839
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "tails-additional-software-config" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:165:in `new'
./features/step_definitions/additional_software_packages.rb:165:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103:in `And I can open the Additional Software configuration window from the notification'
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
After features/support/hooks.rb:515 0.043
After features/support/hooks.rb:326 6.146

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:20:57_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_stable/5455/artifact/build-artifacts/01:20:57_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_stable/5455/artifact/build-artifacts/01:20:57_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.020
3:11.997
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.005
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.196
And I start Tails from USB drive "__internal" with network unplugged 1:1.531
And I enable persistence 13.259
And I remove the "cowsay" deb files from the APT cache 0.073
# 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.085
And I log in to a new session 42.184
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 13.590
And I can open the Additional Software log file from the notification 1:1.075
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-text-editor" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:171:in `new'
./features/step_definitions/additional_software_packages.rb:171:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/additional_software_packages.rb:170:in `block in <top (required)>' (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/additional_software_packages.rb:170:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.057
After features/support/hooks.rb:326 8.753

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:24:16)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:24:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:24:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/01:24:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.009
Tags: @product
1:40.684
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.253
And I start the computer from DVD with network unplugged 38.469
When Tails detects disk read failures on the boot device 1.954
Then I see a disk failure message on the splash screen 1:0.007
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:46:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:15:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'
After features/support/hooks.rb:326 4.848

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 02:06:45)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/02:06:45_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_stable/5455/artifact/build-artifacts/02:06:45_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/02:06:45_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5455/artifact/build-artifacts/02:06:45_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal

After features/support/hooks.rb:100 0.015