Okay; I'm glad you're looking closely at them :-)
BTW I was just looking at a wild java.lang.StackOverflowError of
LeaderElector.retryElection looping recursively, also involving Curator:
https://github.com/apache/solr/actions/runs/11731767672/job/32682507325?pr=2834
On Thu, Nov 7, 2024 at 11:33
With the recent updates in the CLI scripts and JDK version, there are a few
cleanups and optimizations possible in the GC parameters that are passed to
the Solr instance.
Since I am not experienced enough in GC stuff, I'd like some experts to
review https://github.com/apache/solr/pull/2815.
There
Thanks for taking a look David. These are all generally because of Curator,
and I'm going to fix them. They are just taking a bit longer than expected.
- Houston
On Thu, Nov 7, 2024 at 8:16 AM David Smiley wrote:
> Looks like we've got a number of repeatable seed test failures on main --
> http
Thanks for the responses. I paid little attention to the Jira issue and
focused too much on the tests in code, my bad. Consider this a duplicate
and resolved. :)
On Thu, Nov 7, 2024 at 3:23 PM David Smiley wrote:
> Yes; Kevin points out the existing/known issue. In general, search JIRA
> first.
Looks like we've got a number of repeatable seed test failures on main --
https://jenkins.thetaphi.de/job/Solr-main-Linux/21082/#showFailuresLink
If someone's looking into one/more of these, let me know; I may examine one
of the others
On Thu, Nov 7, 2024 at 9:06 AM Policeman Jenkins Server
wrote
Yes; Kevin points out the existing/known issue. In general, search JIRA
first.
I don't recommend adding a feature that nobody actually needs/asked-for.
On Tue, Nov 5, 2024 at 5:16 PM Christos Malliaridis
wrote:
> Looking into the recent JENKINS jobs, one of the failing tests is
>
> java.time.f
