From: Michael Ellerman <mpe@ellerman.id.au>
To: Kevin Hilman <khilman@kernel.org>
Cc: Shuah Khan <shuah.kh@samsung.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Tyler Baker <tyler.baker@linaro.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Testing
Date: Thu, 09 Jul 2015 14:23:53 +1000 [thread overview]
Message-ID: <1436415833.23558.4.camel@ellerman.id.au> (raw)
In-Reply-To: <7hlheqfvqo.fsf@deeprootsystems.com>
On Wed, 2015-07-08 at 09:40 -0700, Kevin Hilman wrote:
>
> Speaking for kernelci.org... with limited time/resources, we'd like to
> focus less on building (others are doing this faster/better) and more on
> boot testing across a wide variety of hardware (e.g for the latest -next
> build, we did ~430 boots on 88 unique boards covering 23 different
> SoCs[1]). We're also in the process of automating kselftest runs on our
> boards.
>
> If we could consume the output of other builders, we'd happily do that
> instead of doing our own builds. Ideally, the builders should produce
> some sort of machine readable data with the build artifacts..
Unfortunately providing build artifacts means you're distributing binaries, and
so life just got complicated. At least for folks like me who work at a company
with too many lawyers.
cheers
next prev parent reply other threads:[~2015-07-09 4:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:24 Mark Brown
2015-07-07 13:02 ` Alexey Dobriyan
2015-07-07 13:14 ` Mark Brown
2015-07-07 18:47 ` Steven Rostedt
2015-07-07 20:46 ` Kees Cook
2015-07-07 22:02 ` Andy Lutomirski
2015-07-08 17:37 ` Mark Brown
2015-07-08 10:43 ` Mark Brown
2015-07-09 10:24 ` Masami Hiramatsu
2015-07-09 12:00 ` Steven Rostedt
2015-07-10 10:39 ` Alexey Dobriyan
2015-07-10 14:02 ` Shuah Khan
2015-07-10 14:28 ` Alexey Dobriyan
2015-07-10 15:05 ` Steven Rostedt
2015-07-10 15:54 ` Shuah Khan
2015-07-07 15:25 ` Guenter Roeck
2015-07-07 17:18 ` Mark Brown
2015-07-07 17:23 ` Julia Lawall
2015-07-07 17:24 ` Shuah Khan
2015-07-07 17:37 ` Guenter Roeck
2015-07-07 17:52 ` Guenter Roeck
2015-07-07 18:28 ` Mark Brown
2015-07-07 22:51 ` Peter Hüwe
2015-07-20 15:53 ` Mel Gorman
2015-07-20 16:39 ` Shuah Khan
2015-07-07 19:21 ` Geert Uytterhoeven
2015-07-08 7:54 ` Dan Carpenter
2015-07-08 8:37 ` Geert Uytterhoeven
2015-07-08 12:10 ` Jiri Kosina
2015-07-08 12:37 ` Josh Boyer
2015-07-08 17:32 ` Mark Brown
2015-07-12 10:21 ` Fengguang Wu
2015-07-08 9:52 ` Mark Brown
2015-07-12 11:15 ` Fengguang Wu
2015-07-13 18:34 ` Mark Brown
2015-07-14 14:22 ` Fengguang Wu
2015-07-14 15:38 ` Mark Brown
2015-07-15 14:21 ` Fengguang Wu
2015-07-08 9:27 ` Michael Ellerman
2015-07-08 13:52 ` Guenter Roeck
2015-07-08 16:40 ` Kevin Hilman
2015-07-08 17:24 ` Guenter Roeck
2015-07-08 18:42 ` Kevin Hilman
2015-07-09 4:23 ` Michael Ellerman [this message]
2015-07-09 18:08 ` Guenter Roeck
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=1436415833.23558.4.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=dan.carpenter@oracle.com \
--cc=khilman@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=shuah.kh@samsung.com \
--cc=tyler.baker@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox