From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(104895-104897) sid(20863) job(DTS_AUTO1001) [V1, 3/3] conf/vm2vm_virtio_net_perf: modify case name
Date: 06 Dec 2021 02:21:42 -0800 [thread overview]
Message-ID: <746b4b$faqtbn@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/104897
Subject: [V1,3/3] conf/vm2vm_virtio_net_perf: modify case name
_Testing issues_
Diff:
test_plans/vm2vm_virtio_net_perf_test_plan.rst
tests/TestSuite_vm2vm_virtio_net_perf.py
conf/vm2vm_virtio_net_perf.cfg
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 0dad4af293e3efbd6de001d9f5a717abb5edfe49
Author: Lewei Yang <leweix.yang@intel.com>
Date: Wed Nov 24 17:23:43 2021 +0000
Comment: tests/mtu_update:igc can receive packets 8 larger than MTU
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
next reply other threads:[~2021-12-06 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:21 sys_stv [this message]
2021-12-06 11:10 sys_stv
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$faqtbn@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).