ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: "Bird, Tim" <Tim.Bird@sonymobile.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference
Date: Sat, 23 Aug 2014 16:12:48 -0500	[thread overview]
Message-ID: <CACxGe6ueac27KTtN_8Uo_BY9KyNVRt8j3p+ak08WuG4j_T+rwg@mail.gmail.com> (raw)
In-Reply-To: <F5184659D418E34EA12B1903EE5EF5FD015DCAE7ABA1@seldmbx02.corpusers.net>

On Sat, Aug 23, 2014 at 8:35 AM, Bird, Tim <Tim.Bird@sonymobile.com> wrote:
> On Friday, August 22, 2014 10:59 AM, Shuah Khan  wrote:
>>
>> On Fri, Aug 22, 2014 at 8:19 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> > Rough notes from the Testing discussion during the workshop day of
>> > Kernel Summit. Big thanks to Paul McKenney for writing all of this
>> > down.
>> >
>>
>> Grant,
>>
>> You beat me to it. Thanks for sending the notes from the discussion and thanks
>> Paul McKenney for writing these down.
>>
>> The next steps on my plate are as follows:
>>
>> Shuah Khan:
>>
>> - Work on putting a basic framework for tests: Pass, Fail, Skip to start with.
>> - update existing tests in tools/testing/selftests to use the
>> framework to serve as an
>>   example for future tests. As we discussed and decided on output will
>> continue to go to
>>   stdio. This will help these tests being used in other scripts that
>> run tests in cross
>>   environments.
>> - Define profiles for short and longer time tests
>> - Add install target in addition to the existing kselftest target at
>> the top level Makefile
>>
>> I will maintain the test framework - will take care of the logistics
>> of MAINTAINER
>> file updates for this and creating a git tree. Individual test
>> maintainers (we have
>> several in MAINTAINERS file) will continue to own and maintain their tests.
>>
>> Fixes to known cross-build failures and new tests are welcome. Please
>> send patches to linux-api mailing list
>
> I've been working on integration with Aboriginal (Rob Landley's
> minimal cross-compile distro) and hope to have some results
> very soon.

I've also been doing some hacking. I've taken a good look at several
of the tools people are using. Guenter's scripts. Kevin & Olof's
scripts, your ttc, and the stuff I'm using personally, and then
started a new tool for booting and testing boards, pulling in bits and
pieces that look good. I've been able to come up with something that
works really well for me, will boot on qemu out-of-the-box, and is
easily extendible to real hardware like a board on a desk or a
personal board farm. I'll post my patches this coming week. Right now
I'm cleaning up some ugly bits and I need to graft in the logging from
Kevin's scripts.

g.

  reply	other threads:[~2014-08-23 21:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` Grant Likely
2014-08-22 17:59   ` Shuah Khan
2014-08-22 18:08     ` Amit Kucheria
2014-08-28 21:54       ` Shuah Khan
2014-08-23 13:35     ` Bird, Tim
2014-08-23 21:12       ` Grant Likely [this message]
2014-08-30  1:09       ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30  2:55         ` Shuah Khan
2014-08-30  5:15           ` Konstantin Ryabitsev
2014-08-23  8:12   ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12     ` Grant Likely
2014-08-24 18:14       ` Guenter Roeck
2014-08-25  9:23         ` Grant Likely
2014-08-25 10:43           ` Guenter Roeck
2014-08-24 18:15       ` Geert Uytterhoeven
2014-08-24 18:37         ` Guenter Roeck
2014-08-24 18:47           ` Olof Johansson
2014-08-24 19:14             ` Jason Cooper
2014-08-24 19:16               ` Jason Cooper

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=CACxGe6ueac27KTtN_8Uo_BY9KyNVRt8j3p+ak08WuG4j_T+rwg@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Tim.Bird@sonymobile.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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