On Sunday 24 February 2008 17:19:58 Will Coleda wrote: > When cutting a release, we do a 'make fulltest', which runs parrot > with various cores to verify that no supported core fails any tests; > the problem with fulltest is that it uses four different harnesses; > This means sifting through a lot of output to find the results for > each core's output; it would be very helpful on this step to have a > single, unified harness.
'make fulltest' exits at the end of any core with failing tests; that's how I expect make to behave. (If it doesn't, there's something wrong.) I'm not sure that this is an argument against adding features to Test.pm, but the problem isn't as bad for me as my reading of this paragraph indicates that it is for you. -- c
