Cucumber Reports (no 3448) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3448	06 Jul 2024, 12:14

Feature: System memory erasure on shutdown

19.016

Scenario Erasure of memory freed by killed userspace processes

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.435

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

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

Output 1

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

When I kill the allocating process 0.273

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

7.826%

7.826% 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: 7.826% (68 MiB out of 876 MiB reference memory)

Hooks

After features/support/hooks.rb:326 5.976

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/00:29:06_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/00:29:06_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/00:29:06_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/00:29:06_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

50.884

Scenario Using a persistent Pidgin configuration

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.006

Steps

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

And the network is plugged 0.046

And Tor is ready 16.459

And available upgrades have been checked 0.041

And all notifications have disappeared 4.180

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

Then I see Pidgin's account manager window 3.387

When I create my XMPP account 3.545

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.033

After features/support/hooks.rb:326 5.009

Output 1

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:39:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/03:39:49_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/03:39:49_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/03:39:49_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/03:39:49_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

28.549

Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile

Steps

When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 6.994

And I cancel the GNOME authentication prompt 1.924

And I unlock and mount this VeraCrypt volume with GNOME Disks 19.630

The

The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
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/veracrypt.rb:280:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'

And I open this VeraCrypt volume in GNOME Files 0.000

Then I see the expected contents in this VeraCrypt volume 0.000

When I lock the currently opened VeraCrypt volume 0.000

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:326 5.533

Output 1

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 04:41:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/04:41:35_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/04:41:35_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/04:41:35_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3448/artifact/build-artifacts/04:41:35_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal

After features/support/hooks.rb:100 0.000