From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(105199) sid(20962) job(DTS_AUTO1028) [V1] test/vf_jumboframe:when driver is ixgbe, dpdk does not need change
Date: 17 Dec 2021 01:07:40 -0800 [thread overview]
Message-ID: <722c05$f374i3@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/105199
Subject: [V1] test/vf_jumboframe:when driver is ixgbe, dpdk does not need change
_Testing issues_
Diff:
tests/TestSuite_vf_jumboframe.py
test_plans/vf_jumboframe_test_plan.rst
DPDK:
commit 042f5a355a57b31a9f87824173a9d427b21abdb8
Author: David Marchand <david.marchand@redhat.com>
Date: Thu Dec 2 19:11:21 2021 +0100
Comment: version: 22.03-rc0
DTS:
commit 8b7a3a50e39c8194608d118a0069155d6d827ce1
Author: Yan Xia <yanx.xia@intel.com>
Date: Fri Dec 10 11:33:36 2021 +0000
Comment: test_plans: modify dpdk app/example to adapt meson name
Test environment and result as below:
+---------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------------+----------+--------------------------------+---------------------------------+
| vf_jumboframe | NIC VF | run | not run |
+---------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/5f9d76c5236e48abbde962aa40ccfaf1
#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 VF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 5/0/0/5/0
with_patch Total/Pass/Fail/Blocked/NA: 5/0/0/5/0
Detail test results:
+----------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+----------------------------------------+------------+---------------+
| vf_jumboframe/test_vf_jumbo_nojumbo | blocked | blocked |
| vf_jumboframe/test_vf_normal_withjumbo | blocked | blocked |
| vf_jumboframe/test_vf_normal_nojumbo | blocked | blocked |
| vf_jumboframe/test_vf_jumbo_overjumbo | blocked | blocked |
| vf_jumboframe/test_vf_jumbo_withjumbo | blocked | blocked |
+----------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2021-12-17 9:07 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='722c05$f374i3@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).