On Tue, Jul 26, 2011 at 11:25:21AM +0700, Nguyen Thai Ngoc Duy wrote: > On Sun, Jul 24, 2011 at 2:16 AM, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote: > > On modern multi-core processors "make test" is often run in multiple jobs. > > If one of them fails the test run does stop, but the concurrently running > > tests finish their run. > > Somewhat related (or not). I change something. I know it breaks things > and want to know _all_ tests it breaks, but "make test" would stop > early. Is there anyway to make it keep going through all tests even if > some fails? "make -j<big number>" improves the situation but does not > really solve it. Try "make -k", which will keep running rules that don't have failed dependencies (in this case, all of the tests are independent, so it will run all of them). Or use "prove", which can do fancy things like putting the last-failed (so you can see the likely failures immediately and start to probe them while the rest of the suite runs). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html