From: "Mark Brown" <broonie@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: kernelci@groups.io, Kevin Hilman <khilman@baylibre.com>
Subject: Re: Some questions about KernelCI
Date: Fri, 30 Aug 2019 20:53:24 +0100 [thread overview]
Message-ID: <20190830195324.GH5182@sirena.co.uk> (raw)
In-Reply-To: <CACT4Y+Zn-q=iAnLttLKSPVAg-u_4sGv4YxT4hfGc+N=UrMf6vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Fri, Aug 30, 2019 at 12:07:47PM -0700, Dmitry Vyukov wrote:
> On Thu, Aug 29, 2019 at 5:14 AM Mark Brown <broonie@kernel.org> wrote:
> > > 2. Are there test coverage reports anywhere? Is it in plans?
> > There's some e-mail reports for tests which are sent to developers at
> > the minute, the web UI is being looked at as well since as you've
> > noticed it's currently not great.
> I meant code coverage reports/stats, which show what's being tested
> and what's not tested.
No, I don't think that's something that's ever done for the kernel in
any sustained fashion.
> > > 4. Do I understand it correctly that test failures are currently not
> > > reported in any way (other than being shown on the dashboard)? Who
> > > looks at the dashboard? Is there constant monitoring of all results?
> > > Is automatic reporting in plans?
> > The test support is pretty much in development at the moment, until
> > we've got the infrastructure working well we're not really pushing on
> > reporting things out too much.
> This equally applies to build and boot testing too. If code does not
> build, this needs to be reported. How does this happen?
The build results are visible via the web site but the main thing for
KernelCI and all the other build testers is that people do some basic
triage and forward on the relevant bits of the e-mail reports.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-30 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 21:03 Some questions about KernelCI Dmitry Vyukov
2019-08-29 12:14 ` Mark Brown
2019-08-30 19:07 ` Dmitry Vyukov
2019-08-30 19:53 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-04 4:07 zhengruoqin
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=20190830195324.GH5182@sirena.co.uk \
--to=broonie@kernel.org \
--cc=dvyukov@google.com \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.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