From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(116053) sid(24598) job(DTS_AUTO_1569) [1/1] test_plans/af_xdp_test_plan.rst: Add test plan for AF_XDP
Date: 16 Sep 2022 02:55:01 -0700 [thread overview]
Message-ID: <11ab82$k8d2a2@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
Test-Label: Intel-dts-pylama-test
Test-Status: FAILURE
http://dpdk.org/patch/116053
Subject: [1/1] test_plans/af_xdp_test_plan.rst: Add test plan for AF_XDP
_Testing issues_
Diff:
tests/TestSuite_af_xdp_2.py
tests/TestSuite_af_xdp.py
test_plans/index.rst
test_plans/af_xdp_test_plan.rst
test_plans/af_xdp_2_test_plan.rst
DPDK:
commit f8f6b1c1744e12d8d6877464a613acd1231db1a1
Author: David Marchand <david.marchand@redhat.com>
Date: Mon Jul 25 22:32:06 2022 +0200
Comment: vhost: stop using mempool for IOTLB cache
DTS:
commit 0c15de88fb78077b4565de70a95220eb835356e1
Author: Song Jiale <songx.jiale@intel.com>
Date: Wed Sep 14 09:42:50 2022 +0000
Comment: tests/ice_flow_priority: synchronize test plans and optimization scripts
PYLAMA test failed information:
framework/ixia_network/ixnet.py:32: [E] E1101 Module 'requests.packages' has no 'urllib3' member [pylint]
framework/multiple_vm.py:6: [E] E0401 Unable to import 'threadpool' [pylint]
framework/pktgen_trex.py:30: [E] E0401 Unable to import 'trex_stl_lib.api' [pylint]
framework/pktgen_trex.py:207: [E] E0401 Unable to import 'trex_stl_lib.api' [pylint]
framework/pktgen_trex.py:454: [E] E0401 Unable to import 'trex_stl_lib.api' [pylint]
DPDK STV team
reply other threads:[~2022-09-16 9:55 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='11ab82$k8d2a2@fmsmga008-auth.fm.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).