From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weix.ling@intel.com
Subject: [dts-test-report] |FAILURE| pw(119572-119574) sid(25635) job(DTS_AUTO_1796) [V1, 3/3] tests/vhost_event_idx_interrupt_cbdma: add new testsuite
Date: 08 Nov 2022 18:26:26 -0800 [thread overview]
Message-ID: <e2f6d4$ipr8t6@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/119574
Subject: [V1,3/3] tests/vhost_event_idx_interrupt_cbdma: add new testsuite
_Testing issues_
Diff:
test_plans/index.rst
test_plans/vhost_event_idx_interrupt_cbdma_test_plan.rst
tests/TestSuite_vhost_event_idx_interrupt_cbdma.py
DPDK:
commit a39f5e14560df310e7af3c135a11bb6f51eb92e6
Author: Rahul Bhansali <rbhansali@marvell.com>
Date: Wed May 25 14:43:27 2022 +0530
Comment: examples/l2fwd: check Rx packets count
DTS:
commit 878a9c7ea3b073956c4efc8cf21ac43454b1b336
Author: Zhimin Huang <zhiminx.huang@intel.com>
Date: Mon Oct 10 07:42:43 2022 +0800
Comment: tests/ice_dcf_qos:modify the command according to the dpdk changed
Test environment and result as below:
+---------------------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------------------+----------+---------------------------------+--------------------------------+
| vhost_event_idx_interrupt_cbdma | CVL Only | run | not run |
+---------------------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/d1a7ac203f7e435ba8222a488b17c79e
Detail execution results:
There were no deltas reported. There may have been an issue with the test harness.
DPDK STV team
reply other threads:[~2022-11-09 2: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='e2f6d4$ipr8t6@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--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).