* [Qemu-devel] RFE for patchew docker result reporting
@ 2018-01-15 11:48 Daniel P. Berrange
2018-01-15 12:26 ` Cornelia Huck
0 siblings, 1 reply; 4+ messages in thread
From: Daniel P. Berrange @ 2018-01-15 11:48 UTC (permalink / raw)
To: qemu-devel, famz
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 :|
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] RFE for patchew docker result reporting
2018-01-15 11:48 [Qemu-devel] RFE for patchew docker result reporting Daniel P. Berrange
@ 2018-01-15 12:26 ` Cornelia Huck
2018-01-16 2:16 ` Fam Zheng
0 siblings, 1 reply; 4+ messages in thread
From: Cornelia Huck @ 2018-01-15 12:26 UTC (permalink / raw)
To: Daniel P. Berrange; +Cc: qemu-devel, famz
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] RFE for patchew docker result reporting
2018-01-15 12:26 ` Cornelia Huck
@ 2018-01-16 2:16 ` Fam Zheng
2018-01-16 9:51 ` Daniel P. Berrange
0 siblings, 1 reply; 4+ messages in thread
From: Fam Zheng @ 2018-01-16 2:16 UTC (permalink / raw)
To: Cornelia Huck; +Cc: Daniel P. Berrange, qemu-devel, famz
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] RFE for patchew docker result reporting
2018-01-16 2:16 ` Fam Zheng
@ 2018-01-16 9:51 ` Daniel P. Berrange
0 siblings, 0 replies; 4+ messages in thread
From: Daniel P. Berrange @ 2018-01-16 9:51 UTC (permalink / raw)
To: Fam Zheng; +Cc: Cornelia Huck, qemu-devel, famz
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 :|
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-01-16 9:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-15 11:48 [Qemu-devel] RFE for patchew docker result reporting Daniel P. Berrange
2018-01-15 12:26 ` Cornelia Huck
2018-01-16 2:16 ` Fam Zheng
2018-01-16 9:51 ` Daniel P. Berrange
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).