Project Number Date
test_Tails_ISO_stable 5605 28 Apr 2025, 20:46

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:11.176
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:511 0.006
Steps
Given a computer 0.243
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:10.933
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:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:300: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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 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
# 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.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
# 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
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:519 0.029
After features/support/hooks.rb:330 14.235 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:20:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:20:36_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_stable/5605/artifact/build-artifacts/01:20:36_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/5605/artifact/build-artifacts/01:20:36_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/5605/artifact/build-artifacts/01:20:36_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.010
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
7:2.951
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:511 0.006
Steps
Given a computer 0.218
And I start Tails from USB drive "__internal" with network unplugged 1:4.379
And I enable persistence 16.171
And I remove the "cowsay" deb files from the APT cache 0.068
# 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.088
And I log in to a new session 40.297
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.726
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/common_steps.rb:599:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:519 0.037
After features/support/hooks.rb:330 10.616 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:27:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:27:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:27:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:27:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:22.347
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.910
And I prepare Tails for memory erasure tests 0.462
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 36.494
And I fill the USB drive with a known pattern 1.345
And I read the content of the test FS 0.082
And patterns cover at least 99% of the test FS size in the guest's memory 3.739 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.295
And I wait for Tails to finish wiping the memory 1:30.017
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.649 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:54:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:54:43_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:54:43_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/01:54:43_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
3:37.817
Scenario Playing an Ogg audio track
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:511 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.783
When I start the Tor Browser 22.967
And the Tor Browser loads the startup page 3:0.066
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/browser.rb:203:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:497:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:40:in `And the Tor Browser loads the startup page'
Then I can listen to an Ogg audio track in Tor Browser 0.000
After features/support/hooks.rb:519 0.043
After features/support/hooks.rb:330 5.983 
SCENARIO FAILED: 'Playing an Ogg audio track' (at time 04:31:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/04:31:13_Playing_an_Ogg_audio_track.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/04:31:13_Playing_an_Ogg_audio_track.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/04:31:13_Playing_an_Ogg_audio_track.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5605/artifact/build-artifacts/04:31:13_Playing_an_Ogg_audio_track.journal
After features/support/hooks.rb:100 0.000