Spike Hung for Almost Two Days
chrisj at rtems.org
Mon Nov 23 23:28:38 UTC 2020
On 24/11/20 8:27 am, Joel Sherrill wrote:
> On Mon, Nov 23, 2020, 2:59 PM Chris Johns <chrisj at rtems.org
> <mailto:chrisj at rtems.org>> wrote:
> On 24/11/20 1:34 am, Joel Sherrill wrote:
> > On Mon, Nov 23, 2020, 8:10 AM Joel Sherrill <joel at rtems.org
> <mailto:joel at rtems.org>
> > <mailto:joel at rtems.org <mailto:joel at rtems.org>>> wrote:
> > Hi
> > I started my Monday by checking in on a build sweep and noticed that a
> > was hung and still running from Saturday. This is on CentOS. Anyone else
> > ever see this from Spike?
> > 0 R joel 24992 24151 99 80 0 - 529380 - Nov21 ?
> > spike --isa=RV64IMAFD
> > ./riscv-rtems6/c/rv64imafd_medany/testsuites/libtests/dl10.exe
> > After sending that, it occurred to me that the RTEMS tester should have
> killed it :(
> Did it try? That test should be tagged user input.
> I don't know. The logs tend to be deleted as it goes. And I've never seen this
> happen before.
I think the tester does a kill with an `exec` type test so a process that is
stuck in a kernel call may ignore the kill.
The point about the user input test is the kill or reset is done once the test
type banner message is seen on the console and I assume that normally happens.
More information about the devel