Project Number Date
test_Tails_ISO_devel 3525 30 Sep 2024, 12:47

Failures Overview

The following summary displays scenarios that failed.

6:47.871
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.005
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.232
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:18.290
And I configure APT to prefer an old version of cowsay 0.026
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 25.788
And I accept adding "cowsay" to Additional Software 5.869
And Additional Software is correctly configured for package "cowsay" 0.855
And I shutdown Tails and wait for the computer to power off 6.331
And I start Tails from USB drive "__internal" with network unplugged 58.110
And I enable persistence 11.881
# 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.023
And I log in to a new session 40.455
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 30.843
And I revert the APT tweaks that made it prefer an old version of cowsay 0.048
# 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.081
And the network is plugged 0.075
And Tor is ready 21.213
# 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 36.305
And available upgrades have been checked 0.523
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.113
And I can open the Additional Software configuration window from the notification 29.800
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Configure" 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:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:164:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:106: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.035
After features/support/hooks.rb:326 5.653

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/01:29:32_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_devel/3525/artifact/build-artifacts/01:29:32_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_devel/3525/artifact/build-artifacts/01:29:32_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/3525/artifact/build-artifacts/01:29:32_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/3525/artifact/build-artifacts/01:29:32_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/3525/artifact/build-artifacts/01:29:32_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/3525/artifact/build-artifacts/01:29:32_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/3525/artifact/build-artifacts/01:29:32_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_devel/3525/artifact/build-artifacts/01:29:32_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.015
2:20.388
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.548
And I prepare Tails for memory erasure tests 0.665
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 35.473
And I fill the USB drive with a known pattern 1.510
And I read the content of the test FS 0.070
And patterns cover at least 99% of the test FS size in the guest's memory 3.252

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I eject the boot medium 0.766
And I wait for Tails to finish wiping the memory 1:30.101
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157: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:326 10.612

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 01:56:00)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/01:56:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/01:56:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/01:56:00_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal

After features/support/hooks.rb:100 0.000
Tags: @product
3:13.839
Scenario MAC address spoofing fails and macchanger returns true
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.472
And I capture all network traffic 0.008
And the network is plugged 0.103
And macchanger will fail by not spoofing and always returns true 0.192
When I log in to a new session 3:5.063
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:562:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:518: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/mac_spoofing.feature:50:in `When I log in to a new session'
Then no network interfaces are enabled 0.000
And no network device leaked the real MAC address 0.000
And I see the "Wired Network Disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:326 5.212

SCENARIO FAILED: 'MAC address spoofing fails and macchanger returns true' (at time 02:50:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/02:50:29_MAC_address_spoofing_fails_and_macchanger_returns_true.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/02:50:29_MAC_address_spoofing_fails_and_macchanger_returns_true.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/02:50:29_MAC_address_spoofing_fails_and_macchanger_returns_true.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3525/artifact/build-artifacts/02:50:29_MAC_address_spoofing_fails_and_macchanger_returns_true.journal

After features/support/hooks.rb:100 0.047