Project Number Date
test_Tails_ISO_devel 3366 29 Apr 2024, 12:40

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.511
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.381
Then the keys trusted by APT are valid for the next 3 months 14.129
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.434 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:23:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/02:23:14_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/02:23:14_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/02:23:14_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/02:23:14_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
4:10.517
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:259 0.008
Before features/support/hooks.rb:456 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.066
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.847
Then I see Pidgin's account manager window 8.177
When I create my XMPP account 15.486
And I close Pidgin's account manager window 0.674
Then Pidgin automatically enables my XMPP account 3:0.264
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/pidgin.rb:149:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:23:in `Then Pidgin automatically enables my XMPP account'
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:464 0.041
After features/support/hooks.rb:305 4.788 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 03:52:46)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:52:46_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:52:46_Chatting_with_some_friend_over_XMPP.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:52:46_Chatting_with_some_friend_over_XMPP.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:52:46_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:89 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:46.783
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:259 0.010
Before features/support/hooks.rb:456 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.215
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.439
Then I see Pidgin's account manager window 3.858
When I create my XMPP account 16.224
And I close Pidgin's account manager window 0.752
Then Pidgin automatically enables my XMPP account 3:0.293
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/pidgin.rb:149:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:36:in `Then Pidgin automatically enables my XMPP account'
When I join some empty multi-user chat 0.000
And I clear the multi-user chat's scrollback 0.000
And my XMPP friend goes online and joins the multi-user chat 0.000
Then I can see that my friend joined the multi-user chat 0.000
And I say something to my friend in the multi-user chat 0.000
Then I receive a response from my friend in the multi-user chat 0.000
When I say https://gitlab.tails.boum.org/tails to my friend in the multi-user chat 0.000
Then I see the Tails GitLab URL 0.000
When I wait 10 seconds 0.000
And I click on the Tails GitLab URL 0.000
Then the Tor Browser loads the Tails GitLab 0.000
After features/support/hooks.rb:464 0.040
After features/support/hooks.rb:305 4.166 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 03:56:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:56:37_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:56:37_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:56:37_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/03:56:37_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:89 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:51.078
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:259 0.009
Before features/support/hooks.rb:456 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.976
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.602
Then I see Pidgin's account manager window 6.605
And I create my XMPP account 17.059
And I close Pidgin's account manager window 0.751
Then Pidgin automatically enables my XMPP account 3:0.084
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/pidgin.rb:149:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:56:in `Then Pidgin automatically enables my XMPP account'
And I can join the "tails" channel on "chat.disroot.org" 0.000
After features/support/hooks.rb:464 0.029
After features/support/hooks.rb:305 4.218 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 04:00:32)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:00:32_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:00:32_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:00:32_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:00:32_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal
After features/support/hooks.rb:89 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
4:7.036
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:259 0.007
Before features/support/hooks.rb:456 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.516
And the network is plugged 0.039
And Tor is ready 19.711
And available upgrades have been checked 1.125
And all notifications have disappeared 4.435
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.559
Then I see Pidgin's account manager window 3.606
When I create my XMPP account 15.111
And I close Pidgin's account manager window 0.829
Then Pidgin automatically enables my XMPP account 3:0.100
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/pidgin.rb:149:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:70:in `Then Pidgin automatically enables my XMPP account'
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
After features/support/hooks.rb:464 0.043
After features/support/hooks.rb:305 4.262 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:04:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:04:44_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:04:44_Using_a_persistent_Pidgin_configuration.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:04:44_Using_a_persistent_Pidgin_configuration.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/04:04:44_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:89 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:4.051
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 22.664
And I unlock and mount this VeraCrypt file container with GNOME Disks 41.386
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Authentication Required" roleName='label'
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/common_steps.rb:761:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:801:in `/^I cancel the GNOME authentication prompt$/'
./features/step_definitions/veracrypt.rb:253:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container 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 file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:305 4.468 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 05:07:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/05:07:50_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/05:07:50_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/05:07:50_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3366/artifact/build-artifacts/05:07:50_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:89 0.014