Re: [dpdk-ci] Intel PerPatch Build

["Xu, Qian Q" <qian.q.xu@intel.com>]

See below inline, thx. 

-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] 
Sent: Monday, November 28, 2016 6:09 PM
To: Xu, Qian Q <qian.q.xu@intel.com>
Cc: ci@dpdk.org; Wei, FangfangX <fangfangx.wei@intel.com>
Subject: Re: Intel PerPatch Build

2016-11-28 07:30, Xu, Qian Q:
> Hi, Thomas
> Pls note that we have updated the per patch Intel compilation check 
> report, and it's the per patch build report. You can get the 
> test-status result from below report. If you have any comments for the 
> report, just feel free to let us know.

Thanks for improving the report.
I have few comments.

The list of test reports is easier to read if every report titles start with [dpdk-test-report] |SUCCESS| (or |FAILURE|) I think you can remove [Intel PerPatch Build] in the title.

---Sure, Fangfang will change it. 

I feel we need to split the report.
What do you think of having a report per OS? or a report per build?
It would show easily how big is the failure by looking at the counters and descriptions in patchwork.
The email volume would be bigger but is it a problem?
----current report is for per patch build report, and for each patch, we now have 18 builds. We will send out 1 build report for 1 patch.  If we send 18 reports for 1 patch, then it may be too many reports. 
If you want to check how many failures for the build, for example, 18 builds, then 1 failures, there is 2 ways to check. 
1. you can get how many failures information from the Build Summary. 
> Patch17274-17274 --> compile pass
> Build Summary: 18 Builds Done, 18 Successful, 0 Failures

2. We can add the failure numbers in the title, such as [dpdk-test-report] |2 FAILURE|xxxxx

Does it make sense? 



You need to use the script send-patch-report.sh.
It will make your reports integrated in patchwork.
---Fangfang will check your scripts and try it. 

If I understand well you test every patches of a series at once and send the report for the last patch of the series?
----No. We send the report for each patch of the series, not the last one. The process of per patch build check is as below. 
1. We pull the patchset, for example, we have 10 patches in 1 patchset. We will apply all the patches to the git tree. 
If apply failed for one tree, we will try other trees(such as next-virtio, next-crypto, next-net), if any tree can be applied, then 
We think the patch apply OK. If all trees can't be applied, we take it as Failure. Then we will send out 10 patch reports, each one is Failure. 

2. If apply patch is OK, then we do per patch build check one by one. After 10 patch's build done, we will send report one by one. 
For example, 10 patches in 1 patchset, we will do 18 builds for each patch, totally 180 builds for the patchset. Then send report for each patch after the last patch. 
Test1: patch1: 18 build
Test2: patch1 + patch2: 18 build
....
Test10: patch1+xxx+patch10: 18build

Is it clear? 

I think it is a good option while waiting for a real series support in patchwork and dpdk-ci scripts.
--We can provide per patch result, no need patchset result. 
 
> Patch17274-17274 --> compile pass
> Build Summary: 18 Builds Done, 18 Successful, 0 Failures