automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, jin.ling@intel.com
Subject: [dts-test-report] |FAILURE| pw(124832) sid(27269) job(DTS_AUTO_2463) [V1, 1/1] tests/uni_pkt: optimize code for check result
Date: 06 Mar 2023 21:26:23 -0800	[thread overview]
Message-ID: <210948$pb591u@orsmga005-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/124832
Subject: [V1,1/1] tests/uni_pkt: optimize code for check result

_Testing issues_

Diff:
	tests/TestSuite_uni_pkt.py

DPDK:
	commit 79cd6f959ebc0886dd212dc4fb057ec2d91b2d39
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Wed Mar 1 17:27:00 2023 +0100
	Comment: doc: add gpudev to the Doxygen index

DTS:
	commit 24c493c04de5eb1c65d5314e4c9b3e563d7016d5
	Author: Jiale Song <songx.jiale@intel.com>
	Date:   Fri Feb 24 16:51:50 2023 +0000
	Comment: tests/iavf_rss_protocol_agnostic_flow: optimize script


Test environment and result as below:
+---------+----------+---------------------------------+--------------------------------+
| suits   | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------+----------+---------------------------------+--------------------------------+
| uni_pkt | NIC PF   | not run                         | run                            |
+---------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/2bd411cfa172405eb748606e8036c29e

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.5 LTS
	Kernel: 5.4.0-135-generic
	CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
	Clang: NA


	Status: FAILURE
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 11/11/0/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 11/10/1/0/0
	
	Detail test results:
	+-----------------------------------+------------+---------------+
	| suit/case                         | with_patch | without_patch |
	+-----------------------------------+------------+---------------+
	| uni_pkt/test_GRE_tunnel           | failed     | passed        |
	| uni_pkt/test_IP_in_IPv4_tunnel    | passed     | passed        |
	| uni_pkt/test_nsh                  | passed     | passed        |
	| uni_pkt/test_NVGRE_in_IPv6_tunnel | passed     | passed        |
	| uni_pkt/test_IPv6_in_IPv4_tunnel  | passed     | passed        |
	| uni_pkt/test_NVGRE_tunnel         | passed     | passed        |
	| uni_pkt/test_l2pkt_detect         | passed     | passed        |
	| uni_pkt/test_IP_in_IPv6_tunnel    | passed     | passed        |
	| uni_pkt/test_Vxlan_tunnel         | passed     | passed        |
	| uni_pkt/test_IPv4_L4              | passed     | passed        |
	| uni_pkt/test_IPv6_L4              | passed     | passed        |
	+-----------------------------------+------------+---------------+

DPDK STV team

             reply	other threads:[~2023-03-07  5:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  5:26 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07  5:13 sys_stv

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='210948$pb591u@orsmga005-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=jin.ling@intel.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).