t; added an extra check in check-source-patterns.groovy though if it's causing
>> folks issues that could be reverted and once overall standardisation is
>> complete then the new validLoggerNamePattern check could be included in the
>> existing validLoggerPattern check.
>>
>&
apache.org/jira/secure/attachment/12925603/SOLR-12419.patch
><https://issues.apache.org/jira/secure/attachment/12925603/SOLR-12419.patch>
>added an extra check in check-source-patterns.groovy though if it's
>causing folks issues that could be reverted and once overall
>standard
lks issues that could be reverted and once overall standardisation is
> complete then the new validLoggerNamePattern check could be included in the
> existing validLoggerPattern check.
>
> Christine
>
> From: dev@lucene.apache.org At: 06/29/18 16:59:51
> To: dev@lucene.apache
/jira/secure/attachment/12925603/SOLR-12419.patch
>added an extra check in check-source-patterns.groovy though if it's
>causing folks issues that could be reverted and once overall
>standardisation is complete then the new validLoggerNamePattern check
>could be included in the existing v
s
>> complete then the new validLoggerNamePattern check could be included in the
>> existing validLoggerPattern check.
>>
>> Christine
>>
>> From: dev@lucene.apache.org At: 06/29/18 16:59:51
>> To: dev@lucene.apache.org
>> Subject: Re: OOM on precommit
&
> existing validLoggerPattern check.
>
> Christine
>
> From: dev@lucene.apache.org At: 06/29/18 16:59:51
> To: dev@lucene.apache.org
> Subject: Re: OOM on precommit
> It’s 64-bit:
>
> java version "1.8.0_152"
> Java(TM) SE Runtime Environment (build 1.8.0_152-
schke
(BLOOMBERG/ LONDON ) , dev@lucene.apache.org
Subject: Re: OOM on precommit
Hi,
Are you sure this causes the problem? The OOM happens on loading a file. Maybe
there's a huge java class file somewhere. Did Steve not update the UAX analyzer?
Uwe
Am June 29, 2018 5:49:22 PM UTC schrieb
e existing validLoggerPattern check.
>
>Christine
>
>From: dev@lucene.apache.org At: 06/29/18 16:59:51To:
>dev@lucene.apache.org
>Subject: Re: OOM on precommit
>
>It’s 64-bit:
>
>java version "1.8.0_152"
>Java(TM) SE Runtime Environment (build 1.8.0_152-b1
ed in the
existing validLoggerPattern check.
Christine
From: dev@lucene.apache.org At: 06/29/18 16:59:51To: dev@lucene.apache.org
Subject: Re: OOM on precommit
It’s 64-bit:
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server V
It’s 64-bit:
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)
It’s a fairly old 1.8 though, I’ll try upgrading
> On 29 Jun 2018, at 16:52, Uwe Schindler wrote:
>
> Could it be a 32 bit Jvm when it fa
Could it be a 32 bit Jvm when it fails? The heap space is different there.
Uwe
Am June 29, 2018 3:45:13 PM UTC schrieb Steve Rowe :
>I just ran “ant precommit” on the tip of branch_7x, and I’m not seeing
>an OOM. My $ANT_OPTS is empty.
>
>$ java -version
>openjdk version "1.8.0_171"
>OpenJDK Run
I just ran “ant precommit” on the tip of branch_7x, and I’m not seeing an OOM.
My $ANT_OPTS is empty.
$ java -version
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-1~bpo8+1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
$ ant -version
Apache An
I’ve started to get this failure whenever I try and run precommit:
validate-source-patterns:
BUILD FAILED
/Users/romseygeek/projects/lucene-solr-7.x/build.xml:128:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at
java.lang.AbstractStrin
13 matches
Mail list logo
