Hi Mike,
yes some checks were relaxed (or got buggy!?) around Java 13/14/15.
Uwe
Am 06.11.2023 um 16:40 schrieb Michael McCandless:
I pushed a fix.
Curious -- the build indeed fails if I use Java 11 on 9.x, but passes
if I use Java 17+.
I'm really confused. Did the javadoc checking get weaker with newer
JDKs? Anyway, I'll port this fix to main.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Nov 6, 2023 at 10:27 AM Apache Jenkins Server
<[email protected]> wrote:
Build:
https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-9.x/6861/
No tests ran.
Build Log:
[...truncated 496 lines...]
BUILD FAILED in 2m 8s
300 actionable tasks: 300 executed
Publishing build scan...
https://ge.apache.org/s/embosyxjwma5i
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test
report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:[email protected]
