Hi,
Here is the PR to disable errorprone with forked compiler:
https://github.com/apache/lucene/pull/12808; it makes no difference in
main, but on 9.x it will fix the issue.
I will merge the commit also to Solr as Jenkins fails there the same way.
Uwe
Am 14.11.2023 um 19:35 schrieb Dawid
What a fantastic test, it found another real bug. I opened
https://github.com/apache/lucene/pull/12807.
On Mon, Nov 13, 2023 at 10:44 PM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-9.x-Linux/14028/
> Java: 64bit/openj9/jdk-17.0.8
Thanks Uwe!
On Tue, Nov 14, 2023 at 7:27 PM Uwe Schindler wrote:
> Hi,
>
> For now the simplest is to disable always is an alternate JVM is used,
> just remove the second part of the first IF statement. In Main it is no
> longer relevant, as the runtime JDK is always >= 17, so it would always
>
Hi,
For now the simplest is to disable always is an alternate JVM is used,
just remove the second part of the first IF statement. In Main it is no
longer relevant, as the runtime JDK is always >= 17, so it would always
trigger the first if.
I would not spend too much time, until errorprone
Hi Dawid,
The problem does not happen on Java 17, because errorprone is not
enabled when the forked JDK is > Java 15. We did this because earlier
versions worked correctly. But new versions of errorprone always fail
when the JDK is forked while compiling.
if (rootProject.usesAltJvm &&
Hi Uwe,
Hah, the issue happens only if you pass CI=true (this is set by CI
> systems), so errorprone is enabled. so do "export CI=true" and then build
> with that config.
>
Darn... I hate that flag. I'll take a look unless you beat me to it.
D.
>
Hi Dawid,
Hah, the issue happens only if you pass CI=true (this is set by CI
systems), so errorprone is enabled. so do "export CI=true" and then
build with that config.
So it looks like a combination of errorprone enabled with Java 11 OpenJ9.
Uwe
Am 13.11.2023 um 09:09 schrieb Dawid Weiss:
Hi Mike,
this comes indirectly from the code formatter. As you see here, the
previous line ends with "}", so it looks like somebody added the
semicolon behind the bracket. This happens often if it was an anonymous
inner class previously or a lambda that was moved around but the
onsolete
It always happens in this config:
Java: 64bit/hotspot/jdk-17.0.9 -XX:+UseCompressedOops -XX:+UseShenandoahGC
Uwe
Am 14.11.2023 um 15:10 schrieb Uwe Schindler:
Hi,
This looks like a JVM bug. It ONLY happens with JDK 17.0.9 (no other
JVM) since last weekend when it was updated. See my other
Hi,
This looks like a JVM bug. It ONLY happens with JDK 17.0.9 (no other
JVM) since last weekend when it was updated. See my other message.
Uwe
Am 14.11.2023 um 14:17 schrieb Michael McCandless:
Hmm again timeout. Something seems amiss. Do our super slow tests
still print out HEARTBEAT
It is absolutely NOT wanted to have absolute timeouts on Policeman
Jenkins. This was hanging really, so it was killed for correct reasons.
Uwe
Am 14.11.2023 um 12:19 schrieb Dawid Weiss:
P.S.: Jenkins kills jobs, if they take longer than usual it kills
it (it has no hard limit, it
Hmm again timeout. Something seems amiss. Do our super slow tests still
print out HEARTBEAT periodically? Or did we lose that in the gradle
migration maybe?
Build timed out (after 126 minutes). Marking the build as aborted.
Build timed out (after 126 minutes). Marking the build as failed.
> P.S.: Jenkins kills jobs, if they take longer than usual it kills it (it
> has no hard limit, it takes the average time of previous runs and if one
> takes much longer it kills).
>
>From what I see here -
https://plugins.jenkins.io/build-timeout/
it should be possible to tweak jenkins to use
Hi,
Sorry, we do not know where it hangs. Phonetic was already finished. As
tasks may run in parallel, we have no idea where it hung.
Uwe
Am 14.11.2023 um 11:56 schrieb Uwe Schindler:
Hi,
It could also be a JVM bug! This happened the second time with Temurin
Hotspot JDK 17.0.9:
Hi,
It could also be a JVM bug! This happened the second time with Temurin
Hotspot JDK 17.0.9:
https://jenkins.thetaphi.de/job/Lucene-main-Linux/45532/ and
https://jenkins.thetaphi.de/job/Lucene-main-Linux/45536/
Both times it hung in phonetic tests...
Uwe
Am 14.11.2023 um 11:46 schrieb
Thanks Uwe.
OK so this might just be a high-sigma outlier-ish event due to unluckily
slow seed selection?
I wonder whether the distribution of total run time of each full "./gradlew
test" on each JVM configuration is roughly Gaussian-ish?
Mike McCandless
http://blog.mikemccandless.com
On
Hi,
Actually this is the default JVM, so its not OpenJ9 or another EA
release.It could be one of the tests haging, but we can't figure that out.
P.S.: Jenkins kills jobs, if they take longer than usual it kills it (it
has no hard limit, it takes the average time of previous runs and if one
Hmm build timed out -- not sure why it's taking so long to run tests:
Build timed out (after 137 minutes). Marking the build as aborted.
Build timed out (after 137 minutes). Marking the build as failed.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Nov 14, 2023 at 1:39 AM Policeman
18 matches
Mail list logo
