[Qemu-devel] RFE for patchew docker result reporting

[Qemu-devel] RFE for patchew docker result reporting

[Daniel P. Berrange]

Currently if I look at the patchew website for build logs, the 'docker'
job results are listed as a single expandable item.

Patchew runs 3 separate docker builds, however, and there's a tonne of
output to scroll through to find which one actually failed.

Thus, my RFE is to split the build log up so that instead of a single
"docker" result, it shows  "docker quick", "docker biuld" and
"docker mingw" as separate build logs / results. This would make it
easier to see at a glance which scenario failed.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: [Qemu-devel] RFE for patchew docker result reporting

[Cornelia Huck]

On Mon, 15 Jan 2018 11:48:41 +0000
"Daniel P. Berrange" <berrange@redhat.com> wrote:

> Currently if I look at the patchew website for build logs, the 'docker'
> job results are listed as a single expandable item.
> 
> Patchew runs 3 separate docker builds, however, and there's a tonne of
> output to scroll through to find which one actually failed.
> 
> Thus, my RFE is to split the build log up so that instead of a single
> "docker" result, it shows  "docker quick", "docker biuld" and
> "docker mingw" as separate build logs / results. This would make it
> easier to see at a glance which scenario failed.

+1. Splitting the output into smaller units makes sense to me.

Re: [Qemu-devel] RFE for patchew docker result reporting

[Fam Zheng]

On Mon, Jan 15, 2018 at 8:26 PM, Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, 15 Jan 2018 11:48:41 +0000
> "Daniel P. Berrange" <berrange@redhat.com> wrote:
>
>> Currently if I look at the patchew website for build logs, the 'docker'
>> job results are listed as a single expandable item.
>>
>> Patchew runs 3 separate docker builds, however, and there's a tonne of
>> output to scroll through to find which one actually failed.
>>
>> Thus, my RFE is to split the build log up so that instead of a single
>> "docker" result, it shows  "docker quick", "docker biuld" and
>> "docker mingw" as separate build logs / results. This would make it
>> easier to see at a glance which scenario failed.
>
> +1. Splitting the output into smaller units makes sense to me.

Made the proposed change on patchew.org. Thanks.

Fam

Re: [Qemu-devel] RFE for patchew docker result reporting

[Daniel P. Berrange]

On Tue, Jan 16, 2018 at 10:16:28AM +0800, Fam Zheng wrote:
> On Mon, Jan 15, 2018 at 8:26 PM, Cornelia Huck <cohuck@redhat.com> wrote:
> > On Mon, 15 Jan 2018 11:48:41 +0000
> > "Daniel P. Berrange" <berrange@redhat.com> wrote:
> >
> >> Currently if I look at the patchew website for build logs, the 'docker'
> >> job results are listed as a single expandable item.
> >>
> >> Patchew runs 3 separate docker builds, however, and there's a tonne of
> >> output to scroll through to find which one actually failed.
> >>
> >> Thus, my RFE is to split the build log up so that instead of a single
> >> "docker" result, it shows  "docker quick", "docker biuld" and
> >> "docker mingw" as separate build logs / results. This would make it
> >> easier to see at a glance which scenario failed.
> >
> > +1. Splitting the output into smaller units makes sense to me.
> 
> Made the proposed change on patchew.org. Thanks.

That's great, thanks for figuring this out so quickly !

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|