[dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci: explicitly call ioport handlers for uio_pci_generic

[dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci: explicitly call ioport handlers for uio_pci_generic

[sys_stv]

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

Test-Label: Intel Niantic on Fedora
Test-Status: SUCCESS

Patchwork ID: 11517-11520
http://www.dpdk.org/dev/patchwork/patch/11520/
Submitter: David Marchand <david.marchand@6wind.com>
Date: Tue, 15 Mar 2016 07:29:10 +0100
DPDK git baseline: 94d8f4bf963a701916b141eed7645f8009aa2054

Check patch:Success

Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-clang: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass



DPDK STV team 

Re: [dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci: explicitly call ioport handlers for uio_pci_generic

[David Marchand]

Hello all,

On Tue, Mar 15, 2016 at 8:05 AM,  <sys_stv@intel.com> wrote:
> Test-Label: Intel Niantic on Fedora
> Test-Status: SUCCESS
>
> Patchwork ID: 11517-11520
> http://www.dpdk.org/dev/patchwork/patch/11520/
> Submitter: David Marchand <david.marchand@6wind.com>
> Date: Tue, 15 Mar 2016 07:29:10 +0100
> DPDK git baseline: 94d8f4bf963a701916b141eed7645f8009aa2054
>
> Check patch:Success
>
> Compilation:
> OS: fedora
> Nic: niantic
> GCC: gcc_x86-64, 4.8.3
> x86_64-native-linuxapp-gcc-combined: compile pass
> i686-native-linuxapp-gcc: compile pass
> x86_64-native-linuxapp-gcc: compile pass
> x86_64-native-linuxapp-clang: compile pass
> x86_64-native-linuxapp-gcc-shared: compile pass
> x86_64-native-linuxapp-gcc-debug: compile pass


Not sure I got a description of what is tested by this tool.

I suppose it applies the 4 patches of the patchset I proposed a bit
earlier on top of the current HEAD.
Does it run checkpatch on each patch ?
Does it check that each patch builds fine individually (I mean in an
incremental way) ?

Any other details ?

Maybe a little description on dpdk.org would help.


Thanks.

-- 
David Marchand

Re: [dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci: explicitly call ioport handlers for uio_pci_generic

[Liu, Yong]

Hi David,

> -----Original Message-----
> From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of
> David Marchand
> Sent: Tuesday, March 15, 2016 3:19 PM
> To: sys_stv
> Cc: test-report@dpdk.org; Thomas Monjalon
> Subject: Re: [dpdk-test-report] [PatchWork]|SUCCESS| pw11517-11520 pci:
> explicitly call ioport handlers for uio_pci_generic
> 
> Hello all,
> 
> On Tue, Mar 15, 2016 at 8:05 AM,  <sys_stv@intel.com> wrote:
> > Test-Label: Intel Niantic on Fedora
> > Test-Status: SUCCESS
> >
> > Patchwork ID: 11517-11520
> > http://www.dpdk.org/dev/patchwork/patch/11520/
> > Submitter: David Marchand <david.marchand@6wind.com>
> > Date: Tue, 15 Mar 2016 07:29:10 +0100
> > DPDK git baseline: 94d8f4bf963a701916b141eed7645f8009aa2054
> >
> > Check patch:Success
> >
> > Compilation:
> > OS: fedora
> > Nic: niantic
> > GCC: gcc_x86-64, 4.8.3
> > x86_64-native-linuxapp-gcc-combined: compile pass
> > i686-native-linuxapp-gcc: compile pass
> > x86_64-native-linuxapp-gcc: compile pass
> > x86_64-native-linuxapp-clang: compile pass
> > x86_64-native-linuxapp-gcc-shared: compile pass
> > x86_64-native-linuxapp-gcc-debug: compile pass
> 
> 
> Not sure I got a description of what is tested by this tool.
> 
> I suppose it applies the 4 patches of the patchset I proposed a bit
> earlier on top of the current HEAD.

Yes, we download your patches from patchwork and do some basic validation before them merged.

> Does it run checkpatch on each patch ?
> Does it check that each patch builds fine individually (I mean in an
> incremental way) ?
> 

By now, we do not run build test for each patch due to time limitation. Patch will be applied in sequence and build with multiple configurations.
We expected that this report should be available asap, as to be reference for developer and maintainer. 

We are improving our system to cover more areas like different OS/support checkpatch and ABI/configuration settings.

> Any other details ?
> 
> Maybe a little description on dpdk.org would help.
> 
> 
Here’s the basic description of patchwork autobuild. The first step, we can add the description in the report.


Patchwork automation build will monitor patch sets status.
If new patch set occurred in http://dpdk.org/dev/patchwork/project/dpdk/list/, automation tool will download it and applied it in latest branch.
If only dpdk driver code modified, patches will be applied in dpdk-next-net repo.
When there's issue in patch apply process, error report will be send to the author and test-report mailing list.

By default build validation will cover 6 different configurations which contained of ICC/clang, share library and debug options.
If there's any document modified, will also build document and check whether build pass.
After all build validations have been done, report email will send to the author and test-report mailing list.
The final report will demonstrate the baseline, build status and build environment.

> Thanks.
> 
> --
> David Marchand