[PATCH libinput 1/2] test: disable coredumps during test suite runs
Peter Hutterer
peter.hutterer at who-t.net
Mon May 8 04:12:02 UTC 2017
Running valgrind through mesontest produces coredumps for a lot of tests
(unclear why, the core dump merely shows a call to abort). But even without
mesontest, creating a core dump for each failed test is a bad idea - if one
fails, most likely many others fail and the coredumps quickly fill up the file
system.
Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
---
test/litest.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/test/litest.c b/test/litest.c
index 9eadc459..62e86da7 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -39,6 +39,7 @@
#include <unistd.h>
#include "linux/input.h"
#include <sys/ptrace.h>
+#include <sys/resource.h>
#include <sys/sendfile.h>
#include <sys/timerfd.h>
#include <sys/wait.h>
@@ -3581,6 +3582,7 @@ litest_list_tests(struct list *tests)
int
main(int argc, char **argv)
{
+ const struct rlimit corelimit = { 0, 0 };
enum litest_mode mode;
list_init(&all_tests);
@@ -3619,6 +3621,9 @@ main(int argc, char **argv)
return EXIT_SUCCESS;
}
+ if (setrlimit(RLIMIT_CORE, &corelimit) == 0)
+ perror("WARNING: Core dumps not disabled. Reason");
+
return litest_run(argc, argv);
}
#endif
--
2.12.2
More information about the wayland-devel
mailing list