On Thu, 2021-09-16 at 14:46 +0200, Alexander Kanavin wrote: > Currently, ptest-runner simply kills the offending test without further ado, > which is not at all helpful when trying to figure out why it happens > (especially if such hangs are intermittent and rare). There's now a script > that gets executed before killing the test, so ideas on what to have in it > are welcome. > > Signed-off-by: Alexander Kanavin <[email protected]> > --- > Makefile | 2 +- > ptest-runner-collect-system-data | 5 +++++ > utils.c | 24 ++++++++++++++++++++++++ > 3 files changed, 30 insertions(+), 1 deletion(-) > create mode 100755 ptest-runner-collect-system-data > > diff --git a/Makefile b/Makefile > index a6372de..168cf5a 100644 > --- a/Makefile > +++ b/Makefile > @@ -43,7 +43,7 @@ $(TEST_EXECUTABLE): $(TEST_OBJECTS) > $(CC) $(LDFLAGS) $(TEST_OBJECTS) -o $@ $(TEST_LIBSTATIC) $(TEST_LDFLAGS) > > check: $(TEST_EXECUTABLE) > - ./$(TEST_EXECUTABLE) -d $(TEST_DATA) > + PATH=.:$(PATH) ./$(TEST_EXECUTABLE) -d $(TEST_DATA) > > .c.o: > $(CC) $(CFLAGS) -c $< -o $@ > diff --git a/ptest-runner-collect-system-data > b/ptest-runner-collect-system-data > new file mode 100755 > index 0000000..5bfeaf3 > --- /dev/null > +++ b/ptest-runner-collect-system-data > @@ -0,0 +1,5 @@ > +#!/bin/sh > +# Other ideas on what to do when a ptest gets stuck welcome. > +pstree -a -l > +df > +free
It is great to see this. I'd suggest dmesg in here since we've seen components of tests segfault before (e.g. lttng-relayd in lttng-tools). Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54743): https://lists.yoctoproject.org/g/yocto/message/54743 Mute This Topic: https://lists.yoctoproject.org/mt/85650481/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
