Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync

[Yonik Seeley]

On Fri, Aug 17, 2012 at 9:42 AM, Steven A Rowe sar...@syr.edu wrote:
 Five out of the last seven builds have failed with this exact same ERROR.

 I can't reproduce on my Win7+Cygwin environment.

 Does anybody know what's happening here?

 If not, I'll ignore this test under Maven.

Pretty strange.  I can't reproduce locally.

multiple values encountered for non multiValued field val_i: [10, 20]

This should be very deterministic (i.e. it should always fail if it
were actually a non multiValued field).
The *_i fields are multivalued according to schema.xml, so this
exception should not happen (the version=1.0 in schema.xml means
multiValued=true by default).

Off of the top of my head, the only thing I can figure is that the
maven based tests are somehow getting the wrong schema sometimes.
Maybe if there's some different with how solr homes are set between
ant and maven?

-Yonik
http://lucidworks.com

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync

[Chris Hostetter]

: Off of the top of my head, the only thing I can figure is that the
: maven based tests are somehow getting the wrong schema sometimes.
: Maybe if there's some different with how solr homes are set between
: ant and maven?

that should be easy to sanity check right?  add something like this into 
the @Before method...

  assertEquals(test-schema-1.0, core.getSchema().getSchemaName())

...and then double check that all of the test schema files have unique 
name attributes in their XML.


-Hoss

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync

[Steven A Rowe]

On August 12th, roughly the same day BasicDistributedZkTest#testDistribSearch 
started failing regularly under the Maven builds, I reduced Solr log output 
under the Maven builds, because Jenkins wasn't sending any notification emails 
when the Maven builds failed, AFAICT because the voluminous Solr logs were 
triggering OOMs in Jenkins JVMs.  (I don't know of a way for 
maven-surefire-plugin to emulate randomizedtesting's 
print-stderr-and-stdout-only-on-failure behavior, so *all* Solr log output was 
ending up in the Jenkins build logs under Maven: 54MB in the last build where 
this was still enabled.)

If it helps, though, there was one build (Lucene-Solr-Maven-4.x build #56) 
under which the failure occurred while full logging was still happening:

https://builds.apache.org/job/Lucene-Solr-Maven-4.x/56/testReport/junit/org.apache.solr.cloud/BasicDistributedZkTest/testDistribSearch/
 

In that log, the schema name is always shown as:

oass.IndexSchema.readSchema Schema name=test

I.e., the version isn't included in the schema name.  (Maybe 
IndexSchema#readSchema should also log the schema version?)

Oh, I may know what's happening: because Maven dependency model can't represent 
the dependencies among solr-core, test-framework, and solrj, the maven builds 
run the solrj and solr-core tests together, and so both modules' resources are 
copied to the same directory.  I see that solrj has a test schema.xml file with 
schema name=test version=1.5.

Steve

-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org] 
Sent: Tuesday, August 28, 2012 5:58 PM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync


: Off of the top of my head, the only thing I can figure is that the
: maven based tests are somehow getting the wrong schema sometimes.
: Maybe if there's some different with how solr homes are set between
: ant and maven?

that should be easy to sanity check right?  add something like this into 
the @Before method...

  assertEquals(test-schema-1.0, core.getSchema().getSchemaName())

...and then double check that all of the test schema files have unique 
name attributes in their XML.


-Hoss

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org