From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(105889-105890) sid(21191) job(DTS_AUTO_389) [V1, 2/2] tests/vm2vm_virtio_net_perf: modify and add test case sync with test plan
Date: 16 Jan 2022 19:56:15 -0800 [thread overview]
Message-ID: <746b4b$fqi24i@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/105890
Subject: [V1,2/2] tests/vm2vm_virtio_net_perf: modify and add test case sync with test plan
_Testing issues_
Diff:
test_plans/vm2vm_virtio_net_perf_test_plan.rst
tests/TestSuite_vm2vm_virtio_net_perf.py
DPDK:
commit 6f716880ee53ac1e50c9c75dc749886e3257bb8f
Author: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Mon Nov 1 13:35:32 2021 +0000
Comment: devtools: remove ugly workaround from get maintainer
DTS:
commit 889a137919cfa520fd7d52a3c42825e3d121b45d
Author: Wei Ling <weix.ling@intel.com>
Date: Fri Jan 14 16:18:49 2022 +0800
Comment: test_plans/*:modify dpdk app name
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
vm2vm_virtio_net_perf_test_plan.rst:363: WARNING: Inconsistent literal block quoting.
vm2vm_virtio_net_perf_test_plan.rst:377: WARNING: Literal block expected; none found.
vm2vm_virtio_net_perf_test_plan.rst:381: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team
reply other threads:[~2022-01-17 3:56 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='746b4b$fqi24i@orsmga008-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).