Thank you so much for clarifying!
Yuting
On Mon, May 16, 2022 at 10:08 AM Uwe Schindler wrote:
> Hi,
>
>
>
> Those loops are fine, the problem is a bug in optimization of Hotspot, it
> is clearly a problem with JDK 17+ which is currently to be fixed. There is
> NOTHING to change in Lucene.
>
>
Hi,
Jenkins runs with JDK 11, so it should hit that problem. Was this in smoke
tester or during normal gradle build?
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Robert Muir
> Sent: Monday, May 16,
Hi,
Those loops are fine, the problem is a bug in optimization of Hotspot, it is
clearly a problem with JDK 17+ which is currently to be fixed. There is NOTHING
to change in Lucene.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:
Hi Uwe,
Thanks for sharing an example of the for loop in the facet code here.
I have been working on some facet code changes recently and have seen this
kind of iterator-based loop several times. I can open a Jira issue and
submit a PR to change these for loops in the facet module.
Best,
Yuting
Hi,
I enabled Policeman Jenkins builds of 9.2.
I will enable ASF Jenkins, too. Takes a few minutes.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Alan Woodward
> Sent: Monday, May 16, 2022 3:59 PM
>
Thanks Mike for stepping up to do 8.11.2!
We recently uncovered some unexpected behavior with SQL LIKE queries
and I'd like to get a fix for
https://issues.apache.org/jira/browse/SOLR-16199 into 8.11.2. Will be
working on it today / tomorrow.
Cheers,
Tim
On Sun, May 15, 2022 at 5:49 PM Gus Heck
NOTICE:
Branch branch_9_2 has been cut and versions updated to 9.3 on stable branch.
Please observe the normal rules:
* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be
committed to the branch. However, you should submit all
On Mon, May 16, 2022 at 9:28 AM Dawid Weiss wrote:
> - different jvms producing different javadoc? Could this be the cause?
>
This is it, it is always a bug when javadoc produces broken links like
this. It happens "at release time" because otherwise nobody is messing
with java 11.
Newer java
It shouldn't be the case. Either something is misconfigured or wrong.
- you can try to diff a clean run with a non-clean run and add
--console=plain and possible --info to gradlew - this will emit more
information about tasks and whether they ran or not,
- different jvms producing different
Hi all,
I was ill at the end of last week so this took a little longer than expected!
I’ve started the release process using the wizard, which has found some broken
links in javadoc. Somewhat strangely, these broken links don’t seem to be
found when not running from a clean checkout, which
That’s again the same bug we have already seen in facet module:
https://bugs.openjdk.java.net/browse/JDK-8283386?focusedCommentId=14496153
Welcome to a new Quality Outreach update!
This time, we have one update but a major one: JEP 425 (Virtual Threads
preview) has been integrated into the OpenJDK mainline! JDK 19
Early-Access builds 22 are the first mainline builds with Virtual
Threads (preview) support. So, Project Loom is now
JVM failure (on JDK 17.0.2!).
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7fe6a986f711, pid=1132974, tid=1137900
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.2+8 (17.0.2+8)
(build 17.0.2+8)
# Java VM: OpenJDK 64-Bit Server VM
13 matches
Mail list logo
