From: Shuah Khan <shuahkh@osg.samsung.com>
To: Prarit Bhargava <prarit@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Shuah Khan <shuah@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Stephen Boyd <stephen.boyd@linaro.org>,
Greg Hackmann <ghackmann@google.com>,
Miroslav Lichvar <mlichvar@redhat.com>,
linux-tip-commits@vger.kernel.org, Josef Bacik <jbacik@fb.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [tip:timers/core] kselftests: timers: set-timer-lat: Tweak reporting when timer fires early
Date: Wed, 20 Sep 2017 17:38:51 -0600 [thread overview]
Message-ID: <bb074fe3-6fca-2250-0c2c-19c0b4afa91d@osg.samsung.com> (raw)
In-Reply-To: <36087647-31b1-95a1-fd74-b22f7d931010@redhat.com>
On 09/20/2017 06:31 AM, Prarit Bhargava wrote:
> On 09/19/2017 11:36 PM, John Stultz wrote:
>> On Tue, Sep 19, 2017 at 6:02 PM, Shuah Khan <shuah@kernel.org> wrote:
>>> Hi Greg,
>>>
>>> On 08/20/2017 03:56 AM, tip-bot for Greg Hackmann wrote:
>>>> Commit-ID: a524b1184b8e86141d689fa78ad150fbf2db9b4c
>>>> Gitweb: http://git.kernel.org/tip/a524b1184b8e86141d689fa78ad150fbf2db9b4c
>>>> Author: Greg Hackmann <ghackmann@google.com>
>>>> AuthorDate: Tue, 25 Jul 2017 14:36:25 -0700
>>>> Committer: John Stultz <john.stultz@linaro.org>
>>>> CommitDate: Thu, 17 Aug 2017 12:14:54 -0700
>>>>
>>>> kselftests: timers: set-timer-lat: Tweak reporting when timer fires early
>>>>
>>>> Rather than printing an error inside the alarm signal handler, set a
>>>> flag that we check later. This keeps the test from spamming the console
>>>> every time the alarm fires early. It also fixes the test exiting with
>>>> error code 0 if this was the only test failure.
>>>>
>>>> Cc: Thomas Gleixner <tglx@linutronix.de>
>>>> Cc: Ingo Molnar <mingo@kernel.org>
>>>> Cc: Miroslav Lichvar <mlichvar@redhat.com>
>>>> Cc: Richard Cochran <richardcochran@gmail.com>
>>>> Cc: Prarit Bhargava <prarit@redhat.com>
>>>> Cc: Stephen Boyd <stephen.boyd@linaro.org>
>>>> Cc: Shuah Khan <shuah@kernel.org>
>>>> Cc: linux-kselftest@vger.kernel.org
>>>> Signed-off-by: Greg Hackmann <ghackmann@google.com>
>>>> Signed-off-by: John Stultz <john.stultz@linaro.org>
>>>
>>> This commit is making the set-timer-lat hang. I reverted this commit
>>> and there is no hang. Could you please take a look and see if this
>>> commit should be reverted.
>>>
>>> make kselftest as well as make -C tools/testing/selftests/timers run_tests
>>> hang.
>>
>> Do you have any specific details as to how the test hangs? (ie: Log
>> data, as in where it might be when it hangs? Any details about the
>> machine?)
>>
>> I'm not seeing it so far in my testing.
>>
>
> I just ran it here and don't see any issues. I'll try on a few other boxes
> to make sure.
>
> # make -C tools/testing/selftests/timers run_tests
John/Prarit,
Thanks for getting back to me. I isolated the problem to redirecting
test output. If I redirect the output it hangs.
./set-timer-lat > /tmp/set-timer-lat 2>&1
it hangs. The reason I am seeing this is because there is a patch
that came in recently to redirect individual test output to a separate
file to make it easier to understand the test results.
Looks like Commits 28be3f8f48cfb3cf024860f042d424cd4824f5f7 and/or
a524b1184b8e86141d689fa78ad150fbf2db9b4c add dependency on stdin/out/err
to the test.
Anyway just an update. It can be reproduced easily. If we have tests
that can't tolerate redirecting output, I might end up dropping the
patch that is in linux-kselftest fixes
fbcab13d2e2511a858590846ac2e2d7cbd830591
So fat set-timer-lat is the only one I found.
thanks,
-- Shuah
next prev parent reply other threads:[~2017-09-20 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-a524b1184b8e86141d689fa78ad150fbf2db9b4c@git.kernel.org>
2017-09-20 1:02 ` Shuah Khan
2017-09-20 3:21 ` John Stultz
2017-09-20 3:36 ` John Stultz
2017-09-20 12:31 ` Prarit Bhargava
2017-09-20 23:38 ` Shuah Khan [this message]
2017-09-21 19:40 ` Greg Hackmann
2017-09-21 19:42 ` Shuah Khan
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=bb074fe3-6fca-2250-0c2c-19c0b4afa91d@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=ghackmann@google.com \
--cc=hpa@zytor.com \
--cc=jbacik@fb.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shuah@kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®