[dpdk-test-report] |SUCCESS| pw37132 [PATCH v2 4/5] net/sfc/base: support FW subvariant choice

[dpdk-test-report] |SUCCESS| pw37132 [PATCH v2 4/5] net/sfc/base: support FW subvariant choice

[sys_stv]

[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]

Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/37132

_Compilation OK_

Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Wed, 4 Apr 2018 15:17:07 +0100
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:34fbfa585cbfa5e3e1de5b0137e91ecfdc87e4f9

Patch37133-37132 --> compile pass
Build Summary: 14 Builds Done, 14 Successful, 0 Failures

Test environment and configuration as below:
OS: FreeBSD10.3_64
    Kernel Version:10.3-RELEASE
    CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-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: FC24_64
    Kernel Version:4.9.13-100.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
OS: UB1604_64
    Kernel Version:4.4.0-78-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-gcc
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-clang
OS: CentOS7_64
    Kernel Version:3.10.0-514.10.2.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-gcc
    x86_64-native-linuxapp-gcc-shared

DPDK STV team

Re: [dpdk-test-report] |SUCCESS| pw37132 [PATCH v2 4/5] net/sfc/base: support FW subvariant choice

[Ferruh Yigit]

On 4/12/2018 7:26 PM, sys_stv@intel.com wrote:
> Test-Label: Intel-compilation
> Test-Status: SUCCESS
> http://dpdk.org/patch/37132
> 
> _Compilation OK_
> 
> Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
> Date: Wed, 4 Apr 2018 15:17:07 +0100
> DPDK git baseline: Repo:dpdk, Branch:master, CommitID:34fbfa585cbfa5e3e1de5b0137e91ecfdc87e4f9
> 
> Patch37133-37132 --> compile pass
> Build Summary: 14 Builds Done, 14 Successful, 0 Failures


Hi Qian, Deepak,

There is a big delay in the build test report, which makes the output useless.

For example this is the build report, just received, for the patch sent on Wed,
4 Apr, 8 days ago. In the peak times like this 8 days latency is too much.

If the reason of the delay is backlog patches, I suggest clean the backlog and
do a clean start, it doesn't have much meaning to get build report of 8 days ago
doesn't have much meaning anyway.


Thanks,
ferruh