theit commented on PR #1345: URL: https://github.com/apache/tika/pull/1345#issuecomment-1727137134
> > ``` > > 4. Running `mvn verify` fails in Tika server core: > > ``` > > > > > > > > > > > > > > > > > > > > > > > > ``` > > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.054 s <<< FAILURE! -- in org.apache.tika.server.core.StackTraceTest > > [ERROR] org.apache.tika.server.core.StackTraceTest.testEmptyParser -- Time elapsed: 0.006 s <<< FAILURE! > > org.opentest4j.AssertionFailedError: bad type: /tika ==> expected: <200> but was: <500> > > at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151) > > (...) > > ``` > > No idea. Let me see if I can reproduce this locally and figure out what's going on. Thank you. Finally I was able to narrow down this behaviour: This obviously depends on the JVM I'm using... Eclipse was configured to use OpenJDK 11 (11.0.20.1 to be precisely) whereas on the command-line OpenJDK 20 (20.0.2) was active. Switching this to also Java 11 makes the error disappear. But: When I use Java 20 in Eclipse to execute the JUnit tests in tika-server-core, 8 of 75 (with 7 skipped) now fail as they did on the command-line. Still investigating... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
