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: [dts-test-report] |FAILURE| pw(104170) sid(20483) job(DTS_AUTO924) [V1] test/rxtx_offload:remove jumboframe test
Date: 11 Nov 2021 04:25:57 -0800	[thread overview]
Message-ID: <311d4e$j55trv@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/104170
Subject: [V1] test/rxtx_offload:remove jumboframe test

_Testing issues_

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

DPDK:
	commit 19d024003dfce0018c9e52635b78efdc6e1c172a
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Mon Nov 8 11:08:08 2021 +0100
	Comment: build: factorize jansson availability check

DTS:
	commit 8b36145c87ae9557a31006a2593200e1aaad422e
	Author: Yu Jiang <yux.jiang@intel.com>
	Date:   Mon Nov 8 15:09:56 2021 +0800
	Comment: tests/pmdrss_hash: replace legacy filter with rte_flow


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/67cdd150c9c841128197e53f96174a21

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


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

DPDK STV team

                 reply	other threads:[~2021-11-11 12:26 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='311d4e$j55trv@fmsmga001-auth.fm.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).