From: sys_stv@intel.com
To: test-report@dpdk.org, nipun.gupta@nxp.com
Cc: longfengx.liang@intel.com, weix.ling@intel.com
Subject: [dpdk-test-report] (Testing) |FAILURE| pw(99860-99869) sid(19214) job(PER_PATCH_BUILD8242) [v7, 9/9] app/bbdev: add test vectors for transport blocks
Date: 30 Sep 2021 07:58:38 -0700 [thread overview]
Message-ID: <f5489b$e6tb1p@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Test-Label: intel-Testing
Test-Status: FAILURE
http://dpdk.org/patch/99869
_Testing issues_
Submitter: Nipun Gupta <nipun.gupta@nxp.com>
Date: 2021-09-28 08:29:45
Branch : dpdk-next-crypto
CommitID: a3309c17dd67b97478dc324b5e3789de0db253d1
Testing Summary : 8 Case Done, 7 Successful, 1 Failures
TestPlan:
pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test.rst
vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test.rst
virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst
TestSuite:
pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
OS : Ubuntu 20.04.3 LTS
Kernel : 5.8.0-48-generic
GCC : 10.3.0-1ubuntu1~20.04
NIC : Ethernet Controller E810-C for SFP
Target : x86_64-native-linuxapp-gcc
Test result details:
+-------------+---------------------+-------+
| suite | case | status|
+-------------+---------------------+-------+
| pf_smoke | test_pf_tx_rx_queue | passed|
| pf_smoke | test_pf_jumbo_frames| passed|
| pf_smoke | test_pf_rss | FAILED|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_jumbo_frames| passed|
| virtio_smoke| test_virtio_pvp | passed|
| virtio_smoke| test_virtio_loopback| passed|
+-------------+---------------------+-------+
DPDK STV team
reply other threads:[~2021-09-30 14:58 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$e6tb1p@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=longfengx.liang@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=test-report@dpdk.org \
--cc=weix.ling@intel.com \
/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).