From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(113402-113404) sid(23752) job(DTS_AUTO_1270) [V2, 3/3] tests/*: add NIC IGC-I226_LM in support suites
Date: 24 Jun 2022 07:02:26 -0700 [thread overview]
Message-ID: <8b0460$igti4j@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Test-Label: Intel-dts-pylama-test
Test-Status: SUCCESS
http://dpdk.org/patch/113404
Subject: [V2,3/3] tests/*: add NIC IGC-I226_LM in support suites
_Testing OK_
Diff:
framework/settings.py
conf/test_case_supportlist.json
conf/test_case_checklist.json
tests/TestSuite_vlan_ethertype_config.py
tests/TestSuite_userspace_ethtool.py
tests/TestSuite_uni_pkt.py
tests/TestSuite_shutdown_api.py
tests/TestSuite_rxtx_offload.py
tests/TestSuite_rss_to_rte_flow.py
tests/TestSuite_qinq_filter.py
tests/TestSuite_pmdrssreta.py
tests/TestSuite_pmdrss_hash.py
tests/TestSuite_mtu_update.py
tests/TestSuite_jumboframes.py
tests/TestSuite_generic_flow_api.py
test_plans/shutdown_api_test_plan.rst
DPDK:
commit 42fbb8e85d1f0b6c1d397d4e7559bc5877ba985e
Author: Don Wallwork <donw@xsightlabs.com>
Date: Thu Jun 23 07:21:27 2022 -0400
Comment: eal/linux: allocate worker lcore stacks in hugepages
DTS:
commit a82eda962a73eb065832418adad3e8d6de77865e
Author: Daxue Gao <daxuex.gao@intel.com>
Date: Wed Jun 22 10:24:02 2022 +0800
Comment: tests/unit_tests: fix self.__name__ error
DPDK STV team
next reply other threads:[~2022-06-24 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:02 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-24 14:01 sys_stv
2022-06-24 11:35 sys_stv
2022-06-24 11:34 sys_stv
2022-06-24 11:33 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='8b0460$igti4j@orsmga001-auth.jf.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).