lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven A Rowe <>
Subject RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync
Date Tue, 28 Aug 2012 23:39:37 GMT
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:


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">.


-----Original Message-----
From: Chris Hostetter [] 
Sent: Tuesday, August 28, 2012 5:58 PM
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.


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message