automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, akihiko.odaki@daynix.com
Subject: [dts-test-report] |SUCCESS| pw(126087-126089) sid(27719) job(DTS_AUTO_2571) [3/3] tests/uni_pkt: Add IGB_1G-82576
Date: 16 Apr 2023 19:26:56 -0700	[thread overview]
Message-ID: <90bd5b$kc9tuv@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/126089
Subject: [3/3] tests/uni_pkt: Add IGB_1G-82576

_Testing OK_

Diff:
	conf/test_case_checklist.json
	tests/TestSuite_pmdrssreta.py
	tests/TestSuite_uni_pkt.py

DPDK:
	commit 3b3fef9de22af80d173453ab65a80b01ce38cbfd
	Author: Elena Agostini <eagostini@nvidia.com>
	Date:   Thu Apr 6 09:49:44 2023 +0000
	Comment: net: fix return type of IPv4 L4 packet checksum

DTS:
	commit 1c14b5d745a3fdc7271d7c18422ffdb06e8510b3
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Fri Mar 31 11:36:36 2023 +0800
	Comment: tests/vhost_user_live_migration: add 2 testcase sync with testplan


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

Log path: /regression_dts/results/test/7d1192ba6c8f484d83f27e597bb378ad

#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: SUCCESS
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 13/13/0/0/0
	
	Detail test results:
	+-----------------------------------+------------+
	| suit/case                         | with_patch |
	+-----------------------------------+------------+
	| pmdrssreta/test_pmdrss_reta       | passed     |
	| pmdrssreta/test_rss_key_size      | passed     |
	| uni_pkt/test_GRE_tunnel           | passed     |
	| uni_pkt/test_IP_in_IPv4_tunnel    | passed     |
	| uni_pkt/test_IP_in_IPv6_tunnel    | passed     |
	| uni_pkt/test_IPv4_L4              | passed     |
	| uni_pkt/test_IPv6_L4              | passed     |
	| uni_pkt/test_IPv6_in_IPv4_tunnel  | passed     |
	| uni_pkt/test_NVGRE_in_IPv6_tunnel | passed     |
	| uni_pkt/test_NVGRE_tunnel         | passed     |
	| uni_pkt/test_Vxlan_tunnel         | passed     |
	| uni_pkt/test_l2pkt_detect         | passed     |
	| uni_pkt/test_nsh                  | passed     |
	+-----------------------------------+------------+

DPDK STV team

             reply	other threads:[~2023-04-17  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  2:26 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-17  2:07 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='90bd5b$kc9tuv@orsmga007-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=dts-test-report@dpdk.org \
    --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).