On 23/08/2017 09:49, Thomas Huth wrote: > While we're at it: I'd like to have a "make check-fast", too. Sometimes > the normal "make check" is already too slow, e.g. while developing new > patches, I sometimes just want to do a very quick sanity test to see > whether I broke some basic things or not, and only do the "make check" > before I submit my patches. > So we would get three stages: > > - make check-fast => For very, very quick sanity tests only > > - make check => E.g. has to be run before submitting patches > > - make check-harder => might run a very long time, so best suited for > nightly regression tests etc.? > > Does that sound reasonable? And the crucial question: Who is going to > implement the basic framework for this?
There's already make check-unit or make check-qtest-x86_64 depending on what you're working on. If you have a many-core machine, of course, there's no simpler solution than throwing more CPUs at it. :) Paolo
