From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(109044) sid(22304) job(DTS_AUTO_718) [v1] tests/unit_tests: Unit Test Deprecation
Date: 31 Mar 2022 20:27:45 -0700 [thread overview]
Message-ID: <8ea9f5$kng92c@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/109044
Subject: [v1] tests/unit_tests: Unit Test Deprecation
_Testing issues_
Diff:
tests/TestSuite_unit_tests_timer.py
tests/TestSuite_unit_tests_ringpmd.py
tests/TestSuite_unit_tests_ring.py
tests/TestSuite_unit_tests_qos.py
tests/TestSuite_unit_tests_power.py
tests/TestSuite_unit_tests_pmd_perf.py
tests/TestSuite_unit_tests_mempool.py
tests/TestSuite_unit_tests_mbuf.py
tests/TestSuite_unit_tests_lpm.py
tests/TestSuite_unit_tests_loopback.py
tests/TestSuite_unit_tests_kni.py
tests/TestSuite_unit_tests_event_timer.py
tests/TestSuite_unit_tests_eal.py
tests/TestSuite_unit_tests_dump.py
tests/TestSuite_unit_tests_cryptodev_func.py
tests/TestSuite_unit_tests_crc.py
tests/TestSuite_unit_tests_cmdline.py
doc/dts_gsg/rel_notes/release_22_04.rst
DPDK:
commit e4e983b975df700474309605b6adb5f2c6d83e2f
Author: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed Mar 9 23:35:08 2022 -0800
Comment: eal/windows: fix data race when creating threads
DTS:
commit 4efb50ddea4010c45976b9f8358b7f4dd77623f6
Author: Jiale Song <songx.jiale@intel.com>
Date: Thu Mar 31 12:43:20 2022 +0000
Comment: tests/distributor: remove dpdk modification
DOC test failed information:
looking for now-outdated files... none found
pickling environment... done
dts_gsg
done
preparing documents... done
writing output... [ 6%] index
DPDK STV team
reply other threads:[~2022-04-01 3:27 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$kng92c@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).