Project Number Date
test_Tails_ISO_devel 3610 12 Dec 2024, 12:52

Failures Overview

The following summary displays scenarios that failed.

8:23.935
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.005
Steps
Given a computer 0.208
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:22.933
And I configure APT to prefer an old version of cowsay 0.029
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 25.796
And I accept adding "cowsay" to Additional Software 6.616
And Additional Software is correctly configured for package "cowsay" 0.890
And I shutdown Tails and wait for the computer to power off 6.449
And I start Tails from USB drive "__internal" with network unplugged 1:6.335
And I enable persistence 12.692
# 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.026
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.093
And I log in to a new session 38.353
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:21.889
And I revert the APT tweaks that made it prefer an old version of cowsay 0.060
# 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.073
And the network is plugged 0.068
And Tor is ready 1:1.418
TCA
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
features/additional_software_packages.feature:100:in `And Tor is ready'
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
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.029
After features/support/hooks.rb:326 14.223

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/01:29:54_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/01:29:54_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/3610/artifact/build-artifacts/01:29:54_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/3610/artifact/build-artifacts/01:29:54_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.018
4:3.003
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 30.298
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.809
Then I see Pidgin's account manager window 4.506
When I create my XMPP account 15.636
And I close Pidgin's account manager window 0.739
Then Pidgin automatically enables my XMPP account 3:0.014
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51: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:515 0.041
After features/support/hooks.rb:326 5.099

SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 03:58:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/03:58:55_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/03:58:55_Chatting_with_some_friend_over_XMPP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/03:58:55_Chatting_with_some_friend_over_XMPP.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/03:58:55_Chatting_with_some_friend_over_XMPP.journal

After features/support/hooks.rb:100 0.000
3:50.651
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.957
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.704
Then I see Pidgin's account manager window 4.061
When I create my XMPP account 15.223
And I close Pidgin's account manager window 0.698
Then Pidgin automatically enables my XMPP account 3:0.006
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51: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:515 0.033
After features/support/hooks.rb:326 5.214

SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 04:02:51)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:02:51_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:02:51_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:02:51_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:02:51_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal

After features/support/hooks.rb:100 0.000
3:46.057
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.673
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.636
Then I see Pidgin's account manager window 3.764
And I create my XMPP account 15.999
And I close Pidgin's account manager window 0.709
Then Pidgin automatically enables my XMPP account 3:0.274
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51: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:515 0.048
After features/support/hooks.rb:326 4.905

SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 04:06:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:06:42_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:06:42_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:06:42_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:06:42_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal

After features/support/hooks.rb:100 0.000
4:14.805
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:269 0.004
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.298
And the network is plugged 0.134
And Tor is ready 22.637
And available upgrades have been checked 1.107
And all notifications have disappeared 4.481
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.490
Then I see Pidgin's account manager window 3.474
When I create my XMPP account 14.413
And I close Pidgin's account manager window 0.666
Then Pidgin automatically enables my XMPP account 3:0.100
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51: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:515 0.040
After features/support/hooks.rb:326 4.884

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:11:02)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:11:02_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:11:02_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:11:02_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3610/artifact/build-artifacts/04:11:02_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000