From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(107925) sid(21776) job(DTS_AUTO_528) [V1] tests/unit_tests_mempool: mempool_perf_autotest increase timeout
Date: 23 Feb 2022 23:44:31 -0800 [thread overview]
Message-ID: <8ea9f5$kcfoii@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/107925
Subject: [V1] tests/unit_tests_mempool: mempool_perf_autotest increase timeout
_Testing issues_
Diff:
tests/TestSuite_unit_tests_mempool.py
DPDK:
commit ee05a93e1e6633d0fdec409faf09f12a2e05b991
Author: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tue Feb 22 09:28:17 2022 +0100
Comment: raw/cnxk_gpio: check pointer before use in self test
DTS:
commit c17f87ae7e0b10af8281373b9017ed77f0c998f3
Author: hanyingya <yingyax.han@intel.com>
Date: Thu Jan 27 10:11:41 2022 +0800
Comment: performance_thread: remove perf test suite
Test environment and result as below:
+--------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+--------------------+----------+---------------------------------+--------------------------------+
| unit_tests_mempool | NIC PF | not run | run |
+--------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/aaa3c2cfc9514d9494c94037e487e315
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-02-24 7:44 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='8ea9f5$kcfoii@fmsmga001-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).