[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g47S16XGSt1ecDR1AnfOSuVwr3o7yma99EEG0GkvQ40gzQ@mail.gmail.com>
Date: Wed, 17 Oct 2018 15:45:32 -0700
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Tim.Bird@...y.com
Cc: kieran.bingham@...asonboard.com,
Greg KH <gregkh@...uxfoundation.org>,
Kees Cook <keescook@...gle.com>, mcgrof@...nel.org,
shuah@...nel.org, Joel Stanley <joel@....id.au>,
mpe@...erman.id.au, joe@...ches.com, brakmo@...com,
rostedt@...dmis.org, khilman@...libre.com,
Julia Lawall <julia.lawall@...6.fr>,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jdike@...toit.com, richard@....at, linux-um@...ts.infradead.org
Subject: Re: [RFC v1 06/31] arch: um: enabled running kunit from User Mode Linux
On Wed, Oct 17, 2018 at 2:18 PM <Tim.Bird@...y.com> wrote:
<snip>
> > There are some
> > other features we would like to add which would help with that goal as
> > well like test isolation. We actually have a presubmit server
> > internally for running KUnit tests that can usually respond to patches
> > with test results within a couple minutes. Would something like that
> > be interesting?
> I think the code and architecture of the software that handles presubmit,
> mail-list scanning, notifications, etc. would be of interest. But KUnit features
> themselves (macro definitions, mocking vs. faking, etc.) would not.
> I only say that in the context of CC-ing the automated testing list on the patch set.
> Of course the KUnit features are interesting by themselves for testers doing
> unit testing.
Fair enough. Well, we will share what we have in that regard, but that
belongs on a separate thread.
BTW, what mailing list is that? I am also guessing your code isn't in
the kernel repo; where is it?
Powered by blists - more mailing lists