From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, ndesaulniers@google.com
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"kernelci.org bot" <bot@kernelci.org>
Subject: Re: next/master build: 227 builds: 17 failed, 210 passed, 41 errors, 497 warnings (next-20200326)
Date: Thu, 26 Mar 2020 20:48:43 +0000 [thread overview]
Message-ID: <20200326204843.GA24981@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOdkTh+uHOK0bd5UGGfYiFQU+MkeT71Yy7Ggof9FkQHCG-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On Thu, Mar 26, 2020 at 11:49:21AM -0700, Nick Desaulniers via Groups.Io wrote:
> Oh no, did the format of the logs change with the latest deployment?
> I expected to see the breakdown of which builds had which
> warnings/errors, which is very fast for me to triage. If it was an
> intentional change, can we please bring those back?
Yes, it was an intentional change due to the huge size of the reports -
the basic issue was including all the successful builds as well which
made it really hard to actually get to the problematic bit of the report
with all the scrolling and deleting. Ideally we'd just be able to
filter those out and leave only the fails, I agree they make it much
easier to triage and report things but it's a more involved change to do
that. Kevin, Guillaume, what do you think?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-26 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e7cb175.1c69fb81.d10e.6d4a@mx.google.com>
2020-03-26 18:49 ` next/master build: 227 builds: 17 failed, 210 passed, 41 errors, 497 warnings (next-20200326) Nick Desaulniers
2020-03-26 20:48 ` Mark Brown [this message]
2020-03-27 3:47 ` Kees Cook
2020-03-27 17:39 ` Nick Desaulniers
2020-03-26 20:54 ` Guillaume Tucker
2020-03-27 17:56 ` Nick Desaulniers
2020-03-31 11:59 ` Guillaume Tucker
2020-03-31 16:30 ` Nick Desaulniers
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=20200326204843.GA24981@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bot@kernelci.org \
--cc=clang-built-linux@googlegroups.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=ndesaulniers@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox