From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, linglix.chen@intel.com
Subject: [dts-test-report] |FAILURE| pw(121170) sid(26211) job(DTS_AUTO_2135) [V1] tests/*: add wait_link_status_up after start testpmd
Date: 21 Dec 2022 01:59:13 -0800 [thread overview]
Message-ID: <510f81$lehbjj@fmsmga004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3046 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/121170
Subject: [V1] tests/*: add wait_link_status_up after start testpmd
_Testing issues_
Diff:
tests/TestSuite_mtu_update.py
tests/TestSuite_external_mempool_handler.py
DPDK:
commit c581c49cd3fcaff596fbe566e270b442e6326c79
Author: Akhil Goyal <gakhil@marvell.com>
Date: Mon Dec 5 13:29:44 2022 +0530
Comment: maintainers: split baseband from crypto tree
DTS:
commit 275fc3485c4b172db8e7b96779850f187ba1bb6f
Author: Yogesh Jangra <yogesh.jangra@intel.com>
Date: Tue Nov 29 06:02:41 2022 +0000
Comment: tests/pipeline: added test case for validate instruction
Test environment and result as below:
+--------------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+--------------------------+----------+--------------------------------+---------------------------------+
| external_mempool_handler | NIC PF | run | not run |
| mtu_update | NIC PF | run | not run |
+--------------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/eed0bce5caf64065b28db3ddb5d48a54
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 22.10
Kernel: 6.0.7-060007-generic
CPU: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
Clang: NA
Status: FAILURE
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 10/5/5/0/0
with_patch Total/Pass/Fail/Blocked/NA: 10/5/5/0/0
Detail test results:
+-------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-------------------------------------------------------+------------+---------------+
| external_mempool_handler/test_mempool_handler_mp_sc | failed | failed |
| external_mempool_handler/test_mempool_handler_sp_mc | failed | failed |
| external_mempool_handler/test_mempool_handler_default | failed | failed |
| external_mempool_handler/test_mempool_handler_stack | failed | failed |
| external_mempool_handler/test_mempool_handler_sp_sc | failed | failed |
| mtu_update/test_mtu_checks_4800 | passed | passed |
| mtu_update/test_mtu_checks_9000 | passed | passed |
| mtu_update/test_mtu_checks_100 | passed | passed |
| mtu_update/test_mtu_checks_1500 | passed | passed |
| mtu_update/test_mtu_checks_2400 | passed | passed |
+-------------------------------------------------------+------------+---------------+
DPDK STV team
next reply other threads:[~2022-12-21 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 9:59 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 9:47 sys_stv
2022-12-21 9:35 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='510f81$lehbjj@fmsmga004-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=linglix.chen@intel.com \
--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).