Cucumber Reports (no 3447) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3447	05 Jul 2024, 12:08

Feature: System memory erasure on shutdown

57.556

Scenario Erasure of the overlayfs read-write branch on shutdown

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I prepare Tails for memory erasure tests 0.453

When I fill a 128 MiB file with a known pattern on the root filesystem 16.074

# ensure the pattern is in memory due to tmpfs, not to disk cache

And I drop all kernel caches 7.073

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

Output 1

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

When I trigger shutdown 0.015

And I wait 20 seconds 20.050

Output 1

Slept for 20 seconds

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

14.414%

14.414% 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:73:in `Then I find very few patterns in the guest's memory'

Output 1

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

Hooks

After features/support/hooks.rb:326 10.589

Output 1

SCENARIO FAILED: 'Erasure of the overlayfs read-write branch on shutdown' (at time 00:30:47)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/00:30:47_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/00:30:47_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/00:30:47_Erasure_of_the_overlayfs_read-write_branch_on_shutdown.journal

After features/support/hooks.rb:100 0.000

Feature: Chatting anonymously using Pidgin

Tags: @product @fragile @check_tor_leaks

49.324

Scenario Using a persistent Pidgin configuration

Hooks

Before features/support/hooks.rb:269 0.008

Before features/support/hooks.rb:507 0.007

Steps

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

And the network is plugged 0.054

And Tor is ready 16.049

And available upgrades have been checked 0.069

And all notifications have disappeared 4.357

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

Then I see Pidgin's account manager window 3.375

When I create my XMPP account 3.508

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:515 0.029

After features/support/hooks.rb:326 5.293

Output 1

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:36:08)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/03:36:08_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/03:36:08_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/03:36:08_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3447/artifact/build-artifacts/03:36:08_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000