From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org, famz@redhat.com
Subject: [Qemu-devel] RFE for patchew docker result reporting
Date: Mon, 15 Jan 2018 11:48:41 +0000 [thread overview]
Message-ID: <20180115114841.GH8218@redhat.com> (raw)
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 :|
next reply other threads:[~2018-01-15 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 11:48 Daniel P. Berrange [this message]
2018-01-15 12:26 ` [Qemu-devel] RFE for patchew docker result reporting Cornelia Huck
2018-01-16 2:16 ` Fam Zheng
2018-01-16 9:51 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180115114841.GH8218@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.