I wonder if this is somehow related to the 'override old definition of datatype junit' message?
On Sep 6, 2010, at 8:20 AM, Antoine Toulme wrote: > Not sure, --trace probably makes the application more verbose and gives back > output as you go. > It might be a setting in the ant runner for junit. > > On Sun, Sep 5, 2010 at 20:41, Mark Petrovic <[email protected]> wrote: > >> My experience with buildr is limited, but I don't remember it buffering >> console output during the test phase. >> >> If I do >> >> $ buildr clean test >> >> the console output pauses here >> >> Running tests in parent:vzservice:vzserver >> Trying to override old definition of datatype junit >> [junit] Testsuite: org.foo.rest.TestIngest >> <pause> >> >> whereupon when the tests (of the JUnit4 variety) finish, I get the full >> console output in one large dump. >> >> But if I do >> >> $ buildr --trace clean test >> >> I can see the individual tests being invoked as they execute. >> >> Is this buffered output normal during the test phase? >> >> >> >> -- >> Mark Petrovic >> >> >> -- Mark Petrovic
