Re: [dpdk-ci] Intel PerPatch Build

[Thomas Monjalon <thomas.monjalon@6wind.com>]

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.

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?

You need to use the script send-patch-report.sh.
It will make your reports integrated in patchwork.

If I understand well you test every patches of a series at once and send the
report for the last patch of the series?
I think it is a good option while waiting for a real series support in patchwork
and dpdk-ci scripts.


> -----Original Message-----
> From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of sys_stv@intel.com
> Sent: Monday, November 28, 2016 2:38 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; test-report@dpdk.org
> Subject: [dpdk-test-report] [Intel PerPatch Build] |SUCCESS| pw17274 [PATCH, v2] maintainers: update testpmd maintainer
> 
> Test-Label: Intel Per-patch compilation check
> Test-Status: SUCCESS
> 
> http://www.dpdk.org/dev/patchwork/patch/17274
> Submitter: Jingjing Wu <jingjing.wu@intel.com>
> Date: Mon, 28 Nov 2016 14:00:50 +0800
> DPDK git baseline: Repo:dpdk, Branch:master, CommitID:3549dd67152d26e46b136286ee0296a9aaa1923d
> 
> Patch17274-17274 --> compile pass
> Build Summary: 18 Builds Done, 18 Successful, 0 Failures
> 
> Test environment and configuration as below:
> OS: FreeBSD10.3_64
>     Kernel Version:10.3-RELEASE
>     CPU info:CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.75-MHz K8-class CPU)
>     GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
>     Clang Version:3.4.1
>     x86_64-native-bsdapp-clang
>     x86_64-native-bsdapp-gcc
> OS: RHEL7.2_64
>     Kernel Version:3.10.0-327.el7.x86_64
>     CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
>     GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
>     Clang Version:3.4.2
>     i686-native-linuxapp-gcc
>     x86_64-native-linuxapp-gcc
>     x86_64-native-linuxapp-gcc-shared
> OS: UB1604_64
>     Kernel Version:4.4.0-47-generic
>     CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
>     GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
>     Clang Version:3.8.0
>     i686-native-linuxapp-gcc
>     x86_64-native-linuxapp-clang
>     x86_64-native-linuxapp-gcc-shared
>     x86_64-native-linuxapp-gcc
> OS: CentOS7_64
>     Kernel Version:3.10.0-327.el7.x86_64
>     CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
>     GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
>     Clang Version:3.4.2
>     i686-native-linuxapp-gcc
>     x86_64-native-linuxapp-clang
>     x86_64-native-linuxapp-gcc-shared
>     x86_64-native-linuxapp-gcc
> OS: FC24_64
>     Kernel Version:4.8.6-201.fc24.x86_64
>     CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
>     GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
>     Clang Version:3.8.0
>     x86_64-native-linuxapp-gcc-debug
>     i686-native-linuxapp-gcc
>     x86_64-native-linuxapp-clang
>     x86_64-native-linuxapp-gcc-shared
>     x86_64-native-linuxapp-gcc
> 
> DPDK STV team