On Fri, Jun 2, 2017 at 9:29 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Thu, Jun 1, 2017 at 7:05 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> Yes, but there is a few issues with this: >> - 'test-suite single file.c' doesn't exit with the right return code yet >> - parallelizing tests with make won't return the summary of the tests >> (which may or may not be needed) >> - the error messages could be mixed in >> - make would stop at the first error (which may be OK or not) >> - would be better used with something like 'test-suite --very-quiet file.c' > > How about the parallel running just run individual test and > save the result/error in per test file. Have the a report target that process > all the individual run result. That will get rid of the result > ordering issue, no > error mix in, no early stop etc. Yes, it's a possibility. > test-suite will need to change a bit for the separate report phrase. > I am not suggesting make that into this series. This series is fine > as it is. I am only making suggestion that parallelizing can speed > up the check run by a few times. Yes, it's how I understood it. I'll see about it next time I make some changes at the testsuite. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
