Well, the unit tests failures that I was seeing seem to have fixed themselves with no code changes or significant changes to my whatsoever. Has anyone else on this list ever seen this:

Failed tests:
testOrderByAscending(org.apache.jackrabbit.test.api.query.SQLOrderByTest) testOrderByDescending(org.apache.jackrabbit.test.api.query.SQLOrderByTest)
  testOrderByDefault(org.apache.jackrabbit.test.api.query.SQLOrderByTest)
testDocOrderIndexedNotation(org.apache.jackrabbit.test.api.query.XPathPosIndexTest) testDocOrderPositionFunction(org.apache.jackrabbit.test.api.query.XPathDocOrderTest) testDocOrderPositionIndex(org.apache.jackrabbit.test.api.query.XPathDocOrderTest) testDocOrderLastFunction(org.apache.jackrabbit.test.api.query.XPathDocOrderTest) testDocOrderFirstFunction(org.apache.jackrabbit.test.api.query.XPathDocOrderTest) testOrderByAscending(org.apache.jackrabbit.test.api.query.XPathOrderByTest) testOrderByDescending(org.apache.jackrabbit.test.api.query.XPathOrderByTest)
  testOrderBy(org.apache.jackrabbit.test.api.query.XPathOrderByTest)

Tests run: 1346, Failures: 11, Errors: 0, Skipped: 0

This is on Mac OS 10.5.1, and like I said, I got those errors for a couple of days and today they are gone. Just for kicks I removed the directory and recreated a source tree from the 1.4 jarfile I'd downloaded a few days ago, and all tests succeeded.

Can anyone think of anything that would be the cause of such an intermittent failure?

Jim

Reply via email to