it is not the smoke test - I ran this:

 python3.2 -u buildAndPushRelease.py -prepare -push simonw -sign
ECA39416 /home/simon/work/projects/lucene/lucene_solr_4_7/ 4.7.0 0

compared to this:

 python3.2 -u buildAndPushRelease.py -prepare -push simonw -sign
ECA39416 -smoke /tmp/lucene_solr_4_7_smoke
/home/simon/work/projects/lucene/lucene_solr_4_7/ 4.7.0 0

the first cmd runs the tests before it builds the release. I disabled
the tests by applying -smoke which skips the test run. This is still
freaking odd - how can I publish a release if the test don't pass a
single time out of 6 runs?

simon


On Tue, Feb 18, 2014 at 1:59 PM, Mark Miller <[email protected]> wrote:
> Weird. The smoke script has always had solr tests disabled. Who enabled it?  
> Those fails in general have JIRA issues as far as I remember.
>
> - Mark
>
>> On Feb 18, 2014, at 7:24 AM, Simon Willnauer <[email protected]> 
>> wrote:
>>
>> hey folks,
>>
>> I try to build an RC to checkout if everything goes alright and I now
>> spend 4 hours already without luck. The release script runs the solr
>> tests but they never pass. I tried it 6 times now and each time a
>> different test breaks. I am going to disable the solr test run in the
>> release script for now to actually run an RC build but this is very
>> concerning IMO. I tried to reproduce the failures each time but they
>> don't reproduce. Its mainly:
>>
>> org.apache.solr.cloud.OverseerTest.testShardAssignmentBigger
>> org.apache.solr.cloud.BasicDistributedZk2Test.testDistribSearch
>> org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
>>
>> any ideas?
>>
>> I mean looking at the CI builds those failures are no news are they?
>>
>> simon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to