automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(97290-97291) [V2, 2/2] test_plans/rxtx_offload: add tx offload multi_segs setting plan
Date: 24 Aug 2021 22:17:45 -0700	[thread overview]
Message-ID: <f5489b$dr4ac0@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-test
Test-Status: FAILURE
http://dpdk.org/patch/97291
Subject: [V2,2/2] test_plans/rxtx_offload: add tx offload multi_segs setting plan

_Testing issues_

Diff:
	tests/TestSuite_rxtx_offload.py
	test_plans/rxtx_offload_test_plan.rst

DPDK:
	commit fdab8f2e17493192d555cd88cf28b06269174326
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Sun Aug 8 21:26:58 2021 +0200
	Comment: version: 21.11-rc0

DTS:
	commit f17c266a14d9655ea0d5a0b0035785f2be767791
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Tue Jul 27 14:29:33 2021 +0800
	Comment: framework/virt_base: add bind_dev parameter in start VM method


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

Log path: /regression_dts/results/test/78d6ac3633b64227979b18687c8594b5

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.2 LTS
	Kernel: 5.8.0-51-generic
	CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
	GCC: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
	Clang: 10.0.0-4ubuntu1


	Status: SUCCESS
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 10/9/0/0/1
	
	Detail test results:
	+---------------------------------------------+-----------+
	| suit/case                                   | with_path |
	+---------------------------------------------+-----------+
	| rxtx_offload/test_txoffload_queue           | passed    |
	| rxtx_offload/test_txoffload_port_cmdline    | passed    |
	| rxtx_offload/test_rxoffload_port            | passed    |
	| rxtx_offload/test_rxoffload_queue           | n/a       |
	| rxtx_offload/test_txoffload_port            | passed    |
	| rxtx_offload/test_txoffload_port_checksum   | passed    |
	| rxtx_offload/test_txoffload_port_multi_segs | passed    |
	| rxtx_offload/test_rxoffload_port_cmdline    | passed    |
	| rxtx_offload/test_rxoffload_port_all        | passed    |
	| rxtx_offload/test_txoffload_port_all        | passed    |
	+---------------------------------------------+-----------+

DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan

rxtx_offload_test_plan.rst:741: WARNING: Unexpected indentation.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team

                 reply	other threads:[~2021-08-25  5:17 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='f5489b$dr4ac0@orsmga007-auth.jf.intel.com' \
    --to=sys_stv@intel.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).