automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(109044) sid(22304) job(DTS_AUTO_766) [v1] tests/unit_tests: Unit Test Deprecation
Date: 19 Apr 2022 20:14:05 -0700	[thread overview]
Message-ID: <8ea9f5$ktu15d@fmsmga001-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

Test-Label: Intel-dts-pylama-test
Test-Status: SUCCESS
http://dpdk.org/patch/109044
Subject: [v1] tests/unit_tests: Unit Test Deprecation

_Testing OK_

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 76076342ec8ef108a155938d46a88bb493fae60e
	Author: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
	Date:   Mon Apr 11 17:15:58 2022 +0200
	Comment: eal: emit warning for unused trylock return value

DTS:
	commit 24ae0a9a40dae26d27aa0ee79a75557135408add
	Author: Yaqi Tang <yaqi.tang@intel.com>
	Date:   Wed Apr 6 22:23:11 2022 +0800
	Comment: tests/cvl_iavf_fdir_pppol2tpoudp: modify test script for more fdir action

DPDK STV team

                 reply	other threads:[~2022-04-20  3:14 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$ktu15d@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).