From: Prarit Bhargava <prarit@redhat.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Thomas Gleixner <tglx@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
Tyler Baker <tyler.baker@linaro.org>
Subject: Re: [PATCH 1/2] kselftests: timers: Make set-timer-lat fail more gracefully for !CAP_WAKE_ALARM
Date: Thu, 02 Apr 2015 06:14:42 -0400 [thread overview]
Message-ID: <551D1692.1050302@redhat.com> (raw)
In-Reply-To: <CALAqxLW65kBPW5knaeGALJnLbGvjRP9Pai6ZiBbePHM1cOppLg@mail.gmail.com>
On 03/26/2015 12:29 PM, John Stultz wrote:
> On Thu, Mar 26, 2015 at 4:31 AM, Prarit Bhargava <prarit@redhat.com> wrote:
>> On 03/25/2015 07:44 PM, John Stultz wrote:
>>> + printf("%-22s %s missing CAP_WAKE_ALARM? : [UNSUPPORTED]\n",
>>> + clockstring(clock_id),
>>> + flags ? "ABSTIME":"RELTIME");
>>
>> Something to think about: Do you want to write these tests to be more human
>> readable or machine readable? In theory with awk I guess it doesn't matter too
>> much, however, it is something that we should think about moving forward.
>
> So this came up at ELC in a few discussions. Right now there isn't any\
Sorry, I'm not familiar with ELC? What is that Acronym for?
> established output format, but there's some nice and simple
> infrastructure for counting pass/fails.
Okay that's great.
>
> However, in talking to Tyler, I know he has started looking at how to
> integrate the selftests into our automated infrastructure and was
> interested in how we improve the output parsing for reports. So there
> is interest in improving this, and I'm open to whatever changes might
> be needed (adding extra arguments to the test to put them into "easy
> parse" mode or whatever).
Thanks John.
P.
>
> thanks
> -john
>
next prev parent reply other threads:[~2015-04-02 10:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 23:44 [PATCH 1/2] kselftests: timers: Make set-timer-lat fail more gracefully for !CAP_WAKE_ALARM John Stultz
2015-03-25 23:44 ` [PATCH 2/2] kselftests: timers: Reduce default runtime on inconsistency-check and set-timer-lat John Stultz
2015-03-26 11:32 ` Prarit Bhargava
2015-03-26 16:20 ` John Stultz
2015-03-31 16:01 ` Shuah Khan
2015-03-31 19:47 ` Shuah Khan
2015-03-26 11:31 ` [PATCH 1/2] kselftests: timers: Make set-timer-lat fail more gracefully for !CAP_WAKE_ALARM Prarit Bhargava
2015-03-26 16:29 ` John Stultz
2015-03-26 17:33 ` Tyler Baker
2015-04-02 10:18 ` Prarit Bhargava
2015-04-02 13:43 ` Shuah Khan
2015-04-02 17:17 ` Tyler Baker
2015-04-02 17:48 ` Shuah Khan
2015-04-02 18:58 ` Tyler Baker
2015-04-02 18:02 ` John Stultz
2015-04-07 14:20 ` Prarit Bhargava
2015-04-08 4:03 ` Michael Ellerman
2015-04-02 10:14 ` Prarit Bhargava [this message]
2015-03-31 15:55 ` Shuah Khan
2015-04-02 3:42 ` John Stultz
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=551D1692.1050302@redhat.com \
--to=prarit@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).