Hi, After updating to revision 1158448 and running a maven clean install, I saw the following:
Failed tests: testBMP(org.apache.tika.parser.image.ImageParserTest): expected:<... > but was:<...> Tests run: 305, Failures: 1, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Apache Tika parent ................................ SUCCESS [0.596s] [INFO] Apache Tika core .................................. SUCCESS [12.997s] [INFO] Apache Tika parsers ............................... FAILURE [25.541s] [INFO] Apache Tika application ........................... SKIPPED [INFO] Apache Tika OSGi bundle ........................... SKIPPED [INFO] Apache Tika ....................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 39.707s [INFO] Finished at: Tue Aug 16 15:16:23 MDT 2011 [INFO] Final Memory: 19M/265M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test (default-test) on project tika-parsers: There are test failures. When I poked at org.apache.tika.parser.image.ImageParserTest.txt I saw: ------------------------------------------------------------------------------- Test set: org.apache.tika.parser.image.ImageParserTest ------------------------------------------------------------------------------- Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec <<< FAILURE! testBMP(org.apache.tika.parser.image.ImageParserTest) Time elapsed: 0.003 sec <<< FAILURE! junit.framework.ComparisonFailure: expected:<... > but was:<...> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.apache.tika.parser.image.ImageParserTest.testBMP(ImageParserTest.java:41) Fair enough. But what is strange is this is an intermittent failure, at least on my machines MBP Pro running Java on Lion, MBP Pro and a Quad Xenon running Java on latest version of Snow Leopard). It pops up on some but not all revisions and I cannot reproduce it. Thoughts? *Steve* * *
