Project Number Date
test_Tails_ISO_stable 4651 05 Feb 2024, 12:24

Failures Overview

The following summary displays scenarios that failed.

7:50.549
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:245 0.006
Before features/support/hooks.rb:442 0.005
Steps
Given a computer 0.230
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:41.929
And I configure APT to prefer an old version of cowsay 0.021
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 22.851
And I accept adding "cowsay" to Additional Software 4.583
And Additional Software is correctly configured for package "cowsay" 0.734
And I shutdown Tails and wait for the computer to power off 5.182
And I start Tails from USB drive "__internal" with network unplugged 56.775
And I enable persistence 33.933
# 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.030
And I log in to a new session 3:4.276
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:554:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:509:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/additional_software_packages.feature:86:in `And I log in to a new session'
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
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
# Note: the next step races against the appearance of the "The
# upgrade of your additional software failed" notification.
# It should win most of the time, which is good, but there's no
# guarantee it does. If it loses, then it'll remove the notification
# we'll be trying to interact with below ("I can open…")
And all notifications have disappeared 0.000
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
After features/support/hooks.rb:450 0.043
After features/support/hooks.rb:291 4.545

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

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:29:35_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_devel/3268/artifact/build-artifacts/01:29:35_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_devel/3268/artifact/build-artifacts/01:29:35_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_devel/3268/artifact/build-artifacts/01:29:35_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_devel/3268/artifact/build-artifacts/01:29:35_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_devel/3268/artifact/build-artifacts/01:29:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:29:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:29:35_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:75 0.016
2:50.613
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:245 0.004
Before features/support/hooks.rb:442 0.004
Steps
Given a computer 0.169
And I start Tails from USB drive "__internal" with network unplugged 57.762
And I enable persistence 35.502
And I remove the "cowsay" deb files from the APT cache 0.725
# 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 38.199
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 9.526
And I can open the Additional Software log file from the notification 28.642
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Show Log" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/additional_software_packages.rb:44:in `click_gnome_shell_notification_button'
./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:129: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:450 0.036
After features/support/hooks.rb:291 4.781

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

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.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_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:32:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:75 0.007
20.283
Scenario Tails erases memory on DVD boot medium removal: vfat
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails from DVD without network and logged in 7.595
And I prepare Tails for memory erasure tests 0.423
And I plug and mount a 128 MiB USB drive with a vfat filesystem 6.828
And I fill the USB drive with a known pattern 2.063
And I read the content of the test FS 0.104
And patterns cover at least 99% of the test FS size in the guest's memory 3.267
97.921% of the test FS size (127.599609375 MiB) has the pattern, but more than 99.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/emergency_shutdown.feature:31:in `And patterns cover at least 99% of the test FS size in the guest's memory'
Output 1

Pattern coverage: 97.921% (124 MiB out of 127 MiB reference memory)

When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:291 3.989

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 01:53:40)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:53:40_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:53:40_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:53:40_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3268/artifact/build-artifacts/01:53:40_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.journal

After features/support/hooks.rb:75 0.000