On 25 July 2017 at 18:42, Steve Muckle <smuckle.linux@gmail.com> wrote:
On Tue, Jul 25, 2017 at 12:03:00PM +0000, Linaro QA wrote:
>
> Tests:   1107

I wonder if folks would benefit from having the number of regressions
listed here above the total number of failures. The subject line as
well perhaps, mentioning the number of new failures since the last
ancestor, instead of the total number of failures?

In this case it says there are 12 failures but most of them have never
passed. This makes for an unnecessarily ominous looking report header
and may initially mislead some folks. Most people I imagine just want to
know if they broke something.

> Failed:  12
> Passed:  1092
> Build:   next-20170725
> Details: https://qa-reports.linaro.org/lkft/linux-next/build/next-20170725
>
> series: lkft
> kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/linux-next/73/defconfig
> build-url: https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=hikey,label=docker-jessie-amd64/73/
> kernel-branch: master
> kernel-describe: next-20170725
> kernel-commit: dce9071ab691f33b2e7e9af142cf95e5ec7cd217
> job_status: Complete

Can the job_status line be removed? I'm guessing it'll always say
complete.
>> There are some jobs that end up incomplete due to fatal timeouts. Those will need to be identified from complete ones just for fixing. I guess this is why this job-status line is there for now...
>> Milosz knows better than me off course in this regard. 

thanks,
steve
_______________________________________________
Lts-dev mailing list
Lts-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lts-dev