: In addition to what Shai mentioned, I wanted to say that there are : other oddities about how the contrib tests run in ant. For example, : I'm not sure why we create the junitfailed.flag files (I think it has : something to do with detecting top-level that a single contrib : failed).
Correct ... even if one contrib fails, test-contrib attempts to run the tests for all the other contribs, and then fails if any junitfailed.flag files are found in any contribs. The assumption was if you were specificly testing a single contrib you'd be using the contrib specific build from it's own directory, and it would still fail fast -- it's only if you run "test-contrib" from the top level that it ignores when "ant test" fails for individual contribs, and then reports the failure at the end. It's a hack, but it's a useful hack for getting nightly builds that can report on the tests for all contribs, even if the first one fails (it's less useful when one contrib depends on another, but that's a more complex issue) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
