[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALCETrWCQyh=QkLU-Zcy7ijb8butWGddvPiuaPuu0-tLd+ur-w@mail.gmail.com>
Date: Mon, 23 Sep 2019 11:10:41 -0700
From: Andy Lutomirski <luto@...nel.org>
To: Petr Vorel <pvorel@...e.cz>
Cc: Richard Palethorpe <rpalethorpe@...e.de>, ltp@...ts.linux.it,
Andy Lutomirski <luto@...nel.org>, LKP <lkp@...org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [LTP] 12abeb544d: ltp.read_all_dev.fail
On Mon, Sep 23, 2019 at 8:39 AM Petr Vorel <pvorel@...e.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
Powered by blists - more mailing lists