Cucumber Reports (no 3414) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3414	04 Jun 2024, 12:58

Feature: System memory erasure on shutdown

19.420

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:265 0.002

Steps

Given I have started Tails from DVD without network and logged in 9.090

And I prepare Tails for memory erasure tests 0.506

When I start a process allocating 128 MiB of memory with a known pattern 1.320

Then patterns cover at least 128 MiB in the guest's memory 3.859

Output 1

Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.319

Then I find very few patterns in the guest's memory 4.323

9.961%

9.961% of the free memory still has the pattern, but less than 0.800% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:219:in `/^I find very few patterns in the guest's memory$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory'

Output 1

Pattern coverage: 9.961% (88 MiB out of 884 MiB reference memory)

Hooks

After features/support/hooks.rb:311 7.136

Output 1

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:39)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/00:28:39_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/00:28:39_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/00:28:39_Erasure_of_memory_freed_by_killed_userspace_processes.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/00:28:39_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000

Feature: Chatting anonymously using Pidgin

Tags: @product @fragile @check_tor_leaks

59.554

Scenario Using a persistent Pidgin configuration

Hooks

Before features/support/hooks.rb:265 0.006

Before features/support/hooks.rb:492 0.011

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.103

And the network is plugged 0.058

And Tor is ready 18.123

And available upgrades have been checked 0.060

And all notifications have disappeared 4.611

When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.586

Then I see Pidgin's account manager window 3.003

When I create my XMPP account 4.006

cannot

cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:149:in `find'
./features/support/helpers/screen.rb:333:in `hover'
./features/support/helpers/screen.rb:360:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:68:in `When I create my XMPP account'

And I close Pidgin's account manager window 0.000

Then Pidgin automatically enables my XMPP account 0.000

When I close Pidgin 0.000

And I take note of the configured Pidgin accounts 0.000

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

Given a computer 0.000

And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000

And Pidgin has the expected persistent accounts configured 0.000

When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000

Then Pidgin automatically enables my XMPP account 0.000

And I join some empty multi-user chat 0.000

# Exercise Pidgin AppArmor profile with persistence enabled.

# This should really be in dedicated scenarios, but it would be

# too costly to set up the virtual USB drive with persistence more

# than once in this feature.

Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000

Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000

And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000

When I close Pidgin's certificate import failure dialog 0.000

And I close Pidgin's certificate manager 0.000

Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000

Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000

And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000

When I close Pidgin's certificate import failure dialog 0.000

And I close Pidgin's certificate manager 0.000

Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000

Hooks

After features/support/hooks.rb:500 0.054

After features/support/hooks.rb:311 5.780

Output 1

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:13:55)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/04:13:55_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/04:13:55_Using_a_persistent_Pidgin_configuration.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/04:13:55_Using_a_persistent_Pidgin_configuration.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3414/artifact/build-artifacts/04:13:55_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000