[dpdk-ci] [DISCUSS] report format for adding checks to other projects

[Tu, Lijuan]

> -----Original Message-----
> From: Aaron Conole <aconole at redhat.com>
> Sent: 2021年3月26日 0:14
> To: Tu, Lijuan <lijuan.tu at intel.com>
> Cc: Ali Alnubani <alialnu at nvidia.com>; ci at dpdk.org; NBU-Contact-Thomas
> Monjalon <thomas at monjalon.net>
> Subject: Re: [DISCUSS] report format for adding checks to other projects
> 
> "Tu, Lijuan" <lijuan.tu at intel.com> writes:
> 
> > Hi Ali,
> >
> >> -----Original Message-----
> >> From: Ali Alnubani <alialnu at nvidia.com>
> >> Sent: 2021年3月15日 21:56
> >> To: Aaron Conole <aconole at redhat.com>; Tu, Lijuan
> >> <lijuan.tu at intel.com>
> >> Cc: ci at dpdk.org; NBU-Contact-Thomas Monjalon <thomas at monjalon.net>
> >> Subject: RE: [DISCUSS] report format for adding checks to other
> >> projects
> >>
> >> Hi Aaron and Lijuan,
> >>
> >> > -----Original Message-----
> >> > From: Ali Alnubani <alialnu at nvidia.com>
> >> > Sent: Thursday, March 11, 2021 5:55 PM
> >> > To: Aaron Conole <aconole at redhat.com>
> >> > Cc: Lijuan Tu <lijuan.tu at intel.com>; ci at dpdk.org;
> >> > NBU-Contact-Thomas Monjalon <thomas at 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 at 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 at intel.com/ but we met another question, which  mail
> > address should dts reports send to ?
> > If reports sent to < test-report at 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?

when you are reading the failure details, and find the reports subject is 
"[dpdk-test-report] [dts-test-report] |FAILURE| pw(89305) <patch subject>"  or "[dpdk-test-report]|FAILURE| pw(89305) <patch subject>"  
Here the tag "[dpdk-test-report]" is added by mail system automatically, and [dts-test-report] is added by dts ci system.
It is very strange for dts developer to see "[dpdk-test-report]" in the mail subject. 
As it is not a key issue, the priority can be very low, I just want maintainer aware of that.

> >>
> >> Regards,
> >> Ali