DPDK CI discussions
 help / color / mirror / Atom feed
* [dpdk-ci] [DISCUSS] report format for adding checks to other projects
@ 2021-03-11 14:52 Aaron Conole
  2021-03-11 15:55 ` Ali Alnubani
  0 siblings, 1 reply; 9+ messages in thread
From: Aaron Conole @ 2021-03-11 14:52 UTC (permalink / raw)
  To: Ali Alnubani; +Cc: Lijuan Tu, ci

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.

Thanks,
Aaron


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-11 14:52 [dpdk-ci] [DISCUSS] report format for adding checks to other projects Aaron Conole
@ 2021-03-11 15:55 ` Ali Alnubani
  2021-03-15 13:56   ` Ali Alnubani
  0 siblings, 1 reply; 9+ messages in thread
From: Ali Alnubani @ 2021-03-11 15:55 UTC (permalink / raw)
  To: Aaron Conole; +Cc: Lijuan Tu, ci, NBU-Contact-Thomas Monjalon

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.

Regards,
Ali

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-11 15:55 ` Ali Alnubani
@ 2021-03-15 13:56   ` Ali Alnubani
  2021-03-25  8:01     ` Tu, Lijuan
  0 siblings, 1 reply; 9+ messages in thread
From: Ali Alnubani @ 2021-03-15 13:56 UTC (permalink / raw)
  To: Aaron Conole, Lijuan Tu; +Cc: ci, NBU-Contact-Thomas Monjalon

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.

Regards,
Ali

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-15 13:56   ` Ali Alnubani
@ 2021-03-25  8:01     ` Tu, Lijuan
  2021-03-25  8:14       ` Thomas Monjalon
  2021-03-25 16:14       ` Aaron Conole
  0 siblings, 2 replies; 9+ messages in thread
From: Tu, Lijuan @ 2021-03-25  8:01 UTC (permalink / raw)
  To: Ali Alnubani, Aaron Conole; +Cc: ci, NBU-Contact-Thomas Monjalon

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?

> 
> Regards,
> Ali

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  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
  1 sibling, 1 reply; 9+ messages in thread
From: Thomas Monjalon @ 2021-03-25  8:14 UTC (permalink / raw)
  To: Ali Alnubani, Aaron Conole, Tu, Lijuan; +Cc: ci

25/03/2021 09:01, Tu, Lijuan:
> 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?

We need to check which change is required in patchwork processing
to have multiple test report mailing lists.
It may take a bit of time. Is it urgent?




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-25  8:14       ` Thomas Monjalon
@ 2021-03-25  8:17         ` Tu, Lijuan
  0 siblings, 0 replies; 9+ messages in thread
From: Tu, Lijuan @ 2021-03-25  8:17 UTC (permalink / raw)
  To: Thomas Monjalon, Ali Alnubani, Aaron Conole; +Cc: ci



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 2021年3月25日 16:15
> To: Ali Alnubani <alialnu@nvidia.com>; Aaron Conole <aconole@redhat.com>;
> Tu, Lijuan <lijuan.tu@intel.com>
> Cc: ci@dpdk.org
> Subject: Re: [DISCUSS] report format for adding checks to other projects
> 
> 25/03/2021 09:01, Tu, Lijuan:
> > 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?
> 
> We need to check which change is required in patchwork processing to have
> multiple test report mailing lists.
> It may take a bit of time. Is it urgent?

No, take your time, thanks


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-25  8:01     ` Tu, Lijuan
  2021-03-25  8:14       ` Thomas Monjalon
@ 2021-03-25 16:14       ` Aaron Conole
  2021-03-26  1:14         ` Tu, Lijuan
  1 sibling, 1 reply; 9+ messages in thread
From: Aaron Conole @ 2021-03-25 16:14 UTC (permalink / raw)
  To: Tu\, Lijuan; +Cc: Ali Alnubani, ci\, NBU-Contact-Thomas Monjalon

"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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-25 16:14       ` Aaron Conole
@ 2021-03-26  1:14         ` Tu, Lijuan
  2021-06-07 16:00           ` Thomas Monjalon
  0 siblings, 1 reply; 9+ messages in thread
From: Tu, Lijuan @ 2021-03-26  1:14 UTC (permalink / raw)
  To: Aaron Conole; +Cc: Ali Alnubani, ci, NBU-Contact-Thomas Monjalon



> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com>
> Sent: 2021年3月26日 0:14
> To: Tu, Lijuan <lijuan.tu@intel.com>
> Cc: Ali Alnubani <alialnu@nvidia.com>; ci@dpdk.org; NBU-Contact-Thomas
> Monjalon <thomas@monjalon.net>
> Subject: Re: [DISCUSS] report format for adding checks to other projects
> 
> "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?

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
  2021-03-26  1:14         ` Tu, Lijuan
@ 2021-06-07 16:00           ` Thomas Monjalon
  0 siblings, 0 replies; 9+ messages in thread
From: Thomas Monjalon @ 2021-06-07 16:00 UTC (permalink / raw)
  To: Tu, Lijuan; +Cc: Aaron Conole, Ali Alnubani, ci

26/03/2021 02:14, Tu, Lijuan:
> From: Aaron Conole <aconole@redhat.com>
> > "Tu, Lijuan" <lijuan.tu@intel.com> writes:
> > > From: Ali Alnubani <alialnu@nvidia.com>
> > > > From: Ali Alnubani <alialnu@nvidia.com>
> > >> > > 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?
> 
> 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.

The new list dts-test-report has been created:
	http://mails.dpdk.org/listinfo/dts-test-report

You can start using it.
Please let me know if patchwork automatically parses it.




^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2021-06-07 16:01 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-11 14:52 [dpdk-ci] [DISCUSS] report format for adding checks to other projects 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
2021-03-26  1:14         ` Tu, Lijuan
2021-06-07 16:00           ` Thomas Monjalon

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ https://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git