From: "Mcnamara, John" <john.mcnamara@intel.com>
To: sys_stv <sys_stv@intel.com>,
"Chen, WeichunX" <weichunx.chen@intel.com>,
"Tang, HaifengX" <haifengx.tang@intel.com>,
"Mo, YufengX" <yufengx.mo@intel.com>,
"Liu, Yong" <yong.liu@intel.com>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"dts@dpdk.org" <dts@dpdk.org>, "Xu, Qian Q" <qian.q.xu@intel.com>,
"Cao, Waterman" <waterman.cao@intel.com>,
"Dong, Shide" <shide.dong@intel.com>
Subject: Re: [dts] |ERROR|pw 7007 [dpdk-dev, v4, 1/1] ip_frag: fix creating ipv6 fragment extension header
Date: Fri, 11 Sep 2015 16:04:52 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202339D55@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2839858.oV9no64RkK@xps13>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, September 10, 2015 10:14 AM
> To: sys_stv
> Cc: Dong, Shide; dts@dpdk.org
> Subject: Re: [dts] |ERROR|pw 7007 [dpdk-dev, v4, 1/1] ip_frag: fix
> creating ipv6 fragment extension header
>
> Thanks for doing some automatic tests.
> Please do not pollute dts list with test reports and use the appropriate
> list
> instead: test-report@dpdk.org.
>
> I think the report would be better readable if there was no array.
> The key/value format is easier and more compact. Example:
> Date: Thu, 10 Sep 2015 09:09:17 +0200
> OS: Fedora
> Failed DTS case: http://dpdk.org/browse/tools/dts/...
Hi,
Good work on the automated testing. It is really nice to see that working now.
I agree with Thomas about the array/table format of the report. It is a little hard to read.
I also agree that a key/value format like the example above would be better.
John.
--
prev parent reply other threads:[~2015-09-11 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 7:52 sys_stv
2015-09-10 9:14 ` Thomas Monjalon
2015-09-11 16:04 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE202339D55@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dts@dpdk.org \
--cc=haifengx.tang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shide.dong@intel.com \
--cc=sys_stv@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yong.liu@intel.com \
--cc=yufengx.mo@intel.com \
/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).