automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: david.marchand@redhat.com
Subject: |SUCCESS|dpdk|80b7993ba1| Intel-Testing
Date: 19 Jun 2024 10:30:50 -0700	[thread overview]
Message-ID: <e8dae2$17vudl@fmviesa008-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3536 bytes --]


Test-Label: intel-Testing
Test-Status: SUCCESS
_Testing PASS_

DPDK git repo: dpdk
commit 80b7993ba1b45d8aad7c294a7aaf66f4cdf860a5
Author: David Marchand <david.marchand@redhat.com>
Date:   Thu Jun 6 14:26:54 2024 +0200

    telemetry: lower log level on socket error
    
    When starting two DPDK programs using the same DPDK prefix (like for
    example OVS and testpmd, both running as primary processes in
    --in-memory mode), the first DPDK process of the two spews some error
    log when the second starts:
    
    TELEMETRY: Socket write base info to client failed
    
    This is because telemetry init involves trying to connect on existing
    sockets to check if it can take over an existing socket file.
    
    On the other hand, this error log provides no helpful information.
    Lower this log to debug level.
    
    Fixes: e14bb5f10509 ("telemetry: fix connected clients count")
    Cc: stable@dpdk.org
    
    Reported-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
    Signed-off-by: David Marchand <david.marchand@redhat.com>
    Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Testing Summary : 18 Case Done, 18 Successful, 0 Failures      

TestPlan:
	pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
	vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
	virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst

TestSuite:
	pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
	vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
	virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py


OS : Ubuntu 22.04.2 LTS       
Kernel : 5.15.0-60-generic         
GCC : 11.3.0-1ubuntu1~22.04        
NIC : Ethernet Controller E810-C for SFP         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| pf_smoke    | test_pf_jumbo_frames      | passed|
	| pf_smoke    | test_pf_rss               | passed|
	| pf_smoke    | test_pf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_jumbo_frames      | passed|
	| vf_smoke    | test_vf_rss               | passed|
	| vf_smoke    | test_vf_tx_rx_queue       | passed|
	| virtio_smoke| test_virtio_loopback      | passed|
	| virtio_smoke| test_virtio_pvp           | passed|
	+-------------+---------------------------+-------+


OS : Ubuntu 22.04.2 LTS       
Kernel : 5.15.0-60-generic         
GCC : 11.3.0-1ubuntu1~22.04        
NIC : Ethernet Controller XL710 for 40GbE QSFP+         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| pf_smoke    | test_pf_jumbo_frames      | passed|
	| pf_smoke    | test_pf_rss               | passed|
	| pf_smoke    | test_pf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_rss               | passed|
	| vf_smoke    | test_vf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_jumbo_frames      | n/a   |
	| virtio_smoke| test_virtio_loopback      | passed|
	| virtio_smoke| test_virtio_pvp           | passed|
	+-------------+---------------------------+-------+


DPDK STV team

                 reply	other threads:[~2024-06-19 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='e8dae2$17vudl@fmviesa008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).