Cucumber Reports (no 3477) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3477	13 Aug 2024, 12:47

Feature: Additional software

11:32.652

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.176

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:16.346

And I configure APT to prefer an old version of cowsay 0.031

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.377

And I accept adding "cowsay" to Additional Software 6.932

And Additional Software is correctly configured for package "cowsay" 0.924

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

And I start Tails from USB drive "__internal" with network unplugged 58.586

And I enable persistence 13.763

# 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.036

And I log in to a new session 37.203

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.747

And I revert the APT tweaks that made it prefer an old version of cowsay 0.062

# 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.081

And the network is plugged 0.072

And Tor is ready 18.551

# Note: the next step races against the appearance of the "The

# upgrade of your additional software failed" notification.

# It should win most of the time, which is good, but there's no

# guarantee it does. If it loses, then it'll remove the notification

# we'll be trying to interact with below ("I can open…")

And all notifications have disappeared 10.185

And available upgrades have been checked 0.802

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.432

And I can open the Additional Software configuration window from the notification 3.375

And I shutdown Tails and wait for the computer to power off 2:7.235

And I start Tails from USB drive "__internal" with network unplugged 58.357

And I enable persistence 11.128

# 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

And I log in to a new session 39.452

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 42.460

And I revert the APT tweaks that made it prefer an old version of cowsay 0.070

And the network is plugged 0.091

And Tor is ready 50.439

Then the Additional Software upgrade service has started 0.228

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.089

Hooks

After features/support/hooks.rb:515 1.150

Error message

Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:08:58:86", mac_daddr="33:33:00:00:00:02", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::e698:cbfa:769c:197e", daddr="ff02::2">
  #<OpenStruct mac_saddr="50:54:00:08:58:86", mac_daddr="52:54:00:dd:ba:ff", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::e698:cbfa:769c:197e", daddr="fe80::5054:ff:fedd:baff">
  #<OpenStruct mac_saddr="50:54:00:08:58:86", mac_daddr="33:33:00:00:00:16", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="fe80::e698:cbfa:769c:197e", daddr="ff02::16">
  #<OpenStruct mac_saddr="50:54:00:08:58:86", mac_daddr="33:33:ff:b2:d8:57", protocol="ipv6", sport=nil, dport=nil, dns_question=[], saddr="::", daddr="ff02::1:ffb2:d857"> (FirewallAssertionFailedError)
./features/support/helpers/firewall_helper.rb:133:in `assert_all_connections'
./features/support/helpers/firewall_helper.rb:143:in `assert_no_leaks'
./features/support/hooks.rb:524:in `After'

After features/support/hooks.rb:326 5.768

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log

Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.pcap

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/01:36:22_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/3477/artifact/build-artifacts/01:36:22_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/3477/artifact/build-artifacts/01:36:22_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.031

Feature: Chatting anonymously using Pidgin

Tags: @product @fragile @check_tor_leaks

59.142

Scenario Using a persistent Pidgin configuration

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.008

Steps

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

And the network is plugged 0.156

And Tor is ready 20.198

And available upgrades have been checked 0.065

And all notifications have disappeared 4.581

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

Then I see Pidgin's account manager window 3.658

When I create my XMPP account 3.752

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

After features/support/hooks.rb:326 5.567

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/03:56:03_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/03:56:03_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/03:56:03_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3477/artifact/build-artifacts/03:56:03_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000