There are 21 failures and 42 errors in the tests when I run the build...
Results :
[surefire] Tests run: 405, Failures: 0, Errors: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16 seconds
[INFO] Finished at: Sun May 28 21:31:58 PDT 2006
[INFO] Final Memory: 13M/24M
[INFO] ------------------------------------------------------------------------
this is in 1.2 trunk, i just checked in a fix for one test that was failing for a patch that was built for post 1.2 release
BTW, shouldn't all the tests pass before committing new code?
in a perfect world yes that would be the case, however sometimes one of us checks in a failing test that another devel will fix/implement (blame tdd), or sometimes we just forget to run the tests or update wicket before doing a checkin. we try to do our best to make sure no tests fail though.
Or is this
just because the devs were in a big hurry to get out the 1.2 release?
1.2 label has no tests failing of course because its a release and we take our time to release those properly
-Igor
