Re: [dpdk-ci] [dpdk-moving] proposal for DPDK CI improvement

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

I'm removing the list moving@dpdk.org as we are discussing implementation details.

2016-11-07 12:20, Xu, Qian Q:
> > a). Currently, there is only " S/W/F for Success/Warning/Fail counters"
> > in tests, so does it refer to build test or functional test or
> > performance test? 
> 
> It can be any test, including performance ones.
> A major performance regression must be seen as a failed test. 
> 
> [Qian] If it refer to any test, so how do we know which test has been
> done. For example, some patch may only do build, some may do perf and
> some may do functional. 
> How to differentiate these tests execution?   

Why do you want to differentiate them in patchwork?

There are 3 views of test reports:
1/ On a patchwork page listing patches, we see the counters S/W/F so
we can give attention to patches having some warnings or failures.
2/ On a patchwork page showing only one patch, we see the list of
tests, the results and the links to the reports.
3/ In a detailed report from the test-report ml archives, we can see
exactly what's going wrong or what was tested successfully (and what
are the numbers in case of a performance test).