Re: [PATCH libinput 1/2] test: disable coredumps during test suite runs

2017-05-08 Thread Peter Hutterer
On Mon, May 08, 2017 at 12:01:05PM +0300, Pekka Paalanen wrote: > On Mon, 8 May 2017 18:35:33 +1000 > Peter Hutterer wrote: > > > On Mon, May 08, 2017 at 02:12:02PM +1000, Peter Hutterer wrote: > > > Running valgrind through mesontest produces coredumps for a lot of tests > > > (unclear why, the

Re: [PATCH libinput 1/2] test: disable coredumps during test suite runs

2017-05-08 Thread Pekka Paalanen
On Mon, 8 May 2017 18:35:33 +1000 Peter Hutterer wrote: > On Mon, May 08, 2017 at 02:12:02PM +1000, Peter Hutterer wrote: > > 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, cre

Re: [PATCH libinput 1/2] test: disable coredumps during test suite runs

2017-05-08 Thread Peter Hutterer
On Mon, May 08, 2017 at 02:12:02PM +1000, Peter Hutterer wrote: > 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 > fa

[PATCH libinput 1/2] test: disable coredumps during test suite runs

2017-05-07 Thread Peter Hutterer
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