From: Andy Lutomirski <luto@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.de>,
ltp@lists.linux.it, Andy Lutomirski <luto@kernel.org>,
LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LTP] 12abeb544d: ltp.read_all_dev.fail
Date: Mon, 23 Sep 2019 11:10:41 -0700 [thread overview]
Message-ID: <CALCETrWCQyh=QkLU-Zcy7ijb8butWGddvPiuaPuu0-tLd+ur-w@mail.gmail.com> (raw)
In-Reply-To: <20190923153908.GA379@dell5510>
On Mon, Sep 23, 2019 at 8:39 AM Petr Vorel <pvorel@suse.cz> wrote:
>
> Hi,
>
> > > FYI, we noticed the following commit (built with gcc-7):
>
> > > commit: 12abeb544d548f55f56323fc6e5e6c0fb74f58e1 ("horrible test hack")
> > > https://kernel.googlesource.com/pub/scm/linux/kernel/git/luto/linux.git random/kill-it
>
> ...
> > > tst_test.c:1108: INFO: Timeout per run is 0h 05m 00s
> > > Test timeouted, sending SIGKILL!
> > > tst_test.c:1148: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
> > > tst_test.c:1149: BROK: Test killed! (timeout?)
>
> > So perhaps this is caused by reads of /dev/random hanging?
>
> > At any rate,
> > I suppose this is intended to deliberately break something, so we can
> > ignore it.
> Yep, I'd ignore it, [1] really looks like the commit description "horrible test hack" :)
>
Indeed. I should have pushed this to my not-for-automated-testing tree.
--Andy
prev parent reply other threads:[~2019-09-23 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 0:38 12abeb544d: ltp.read_all_dev.fail kernel test robot
2019-09-23 8:11 ` [LTP] " Richard Palethorpe
2019-09-23 15:39 ` Petr Vorel
2019-09-23 18:10 ` Andy Lutomirski [this message]
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='CALCETrWCQyh=QkLU-Zcy7ijb8butWGddvPiuaPuu0-tLd+ur-w@mail.gmail.com' \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rpalethorpe@suse.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;
as well as URLs for NNTP newsgroup(s).