From: Aaron Conole <aconole@redhat.com>
To: "Tu\, Lijuan" <lijuan.tu@intel.com>
Cc: Ali Alnubani <alialnu@nvidia.com>, "ci\@dpdk.org" <ci@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
Date: Thu, 25 Mar 2021 12:14:21 -0400 [thread overview]
Message-ID: <f7tsg4j1a8y.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <0bdc529461824da6943acc968fb41e3f@intel.com> (Lijuan Tu's message of "Thu, 25 Mar 2021 08:01:17 +0000")
"Tu, Lijuan" <lijuan.tu@intel.com> writes:
> Hi Ali,
>
>> -----Original Message-----
>> From: Ali Alnubani <alialnu@nvidia.com>
>> Sent: 2021年3月15日 21:56
>> To: Aaron Conole <aconole@redhat.com>; Tu, Lijuan <lijuan.tu@intel.com>
>> Cc: ci@dpdk.org; NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
>> Subject: RE: [DISCUSS] report format for adding checks to other projects
>>
>> Hi Aaron and Lijuan,
>>
>> > -----Original Message-----
>> > From: Ali Alnubani <alialnu@nvidia.com>
>> > Sent: Thursday, March 11, 2021 5:55 PM
>> > To: Aaron Conole <aconole@redhat.com>
>> > Cc: Lijuan Tu <lijuan.tu@intel.com>; ci@dpdk.org; NBU-Contact-Thomas
>> > Monjalon <thomas@monjalon.net>
>> > Subject: Re: [DISCUSS] report format for adding checks to other
>> > projects
>> >
>> > Hi Aaron,
>> >
>> > > Hi Ali,
>> > >
>> > > There was a question today about submitting test reports for patches
>> > > that belong to other projects. Specifically, the DTS project (found
>> > > at
>> > > http://patches.dpdk.org/project/dts/list/)
>> > >
>> > > I believe there is no need to do anything different (because patch
>> > > ID should be unique across the patchwork instance, so the test
>> > > report will go to the correct patch), but wanted to confirm this is correct.
>> > >
>> >
>> > Same report format should work fine, but we have to make the Patchwork
>> > user CI <ci@dpdk.org> a maintainer for these projects. We'll do that
>> > soon and update.
>> >
>>
>> The CI user is now a maintainer for the DTS project.
>> Please let me know if you see any issues with creating checks via email reports.
>
> We sent reports to dts project, and it works,
> e.g. http://patches.dpdk.org/project/dts/patch/1615946979-23566-1-git-send-email-hailinx.xu@intel.com/
> but we met another question, which mail address should dts reports send to ?
> If reports sent to < test-report@dpdk.org>, it will be mixed with dpdk
> reports,
> e.g. http://mails.dpdk.org/archives/test-report/2021-March/183128.html
> And an tag [dpdk-test-report] will be added automatically, it's very confused for users.
> Therefore, Can we have a separated mail address for dts reports?
Is it really a problem to intermingle? I think most of the 'users' of
this list will access via the patchwork front-end, yes?
>>
>> Regards,
>> Ali
next prev parent reply other threads:[~2021-03-25 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:52 Aaron Conole
2021-03-11 15:55 ` Ali Alnubani
2021-03-15 13:56 ` Ali Alnubani
2021-03-25 8:01 ` Tu, Lijuan
2021-03-25 8:14 ` Thomas Monjalon
2021-03-25 8:17 ` Tu, Lijuan
2021-03-25 16:14 ` Aaron Conole [this message]
2021-03-26 1:14 ` Tu, Lijuan
2021-06-07 16:00 ` Thomas Monjalon
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=f7tsg4j1a8y.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=thomas@monjalon.net \
/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).