From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, hongbox.li@intel.com
Subject: [dts-test-report] |SUCCESS| pw(124664) sid(27220) job(DTS_AUTO_2452) [V1] tests/dcf_lifecycle: optimize script
Date: 02 Mar 2023 01:48:52 -0800 [thread overview]
Message-ID: <17e395$mohjsr@fmsmga003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Test-Label: Intel-dts-pylama-test
Test-Status: SUCCESS
http://dpdk.org/patch/124664
Subject: [V1] tests/dcf_lifecycle: optimize script
_Testing OK_
Diff:
tests/TestSuite_dcf_lifecycle.py
DPDK:
commit 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Thu Jan 5 16:18:38 2023 +0100
Comment: eal/windows: fix pedantic build
DTS:
commit 11b6c1ea068db82d415f2ae0c042963d956daf69
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Thu Feb 2 13:53:18 2023 +0800
Comment: version: 23.03-rc0
DPDK STV team
reply other threads:[~2023-03-02 9:48 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='17e395$mohjsr@fmsmga003-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=hongbox.li@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).