janhoy opened a new pull request, #3937:
URL: https://github.com/apache/solr/pull/3937
On Crave runs, about one failure per week.
```
> Task :solr:core:wipeTaskTemp
ERROR: The following test(s) have failed:
- org.apache.solr.client.solrj.impl.LB2SolrClientTest.testTwoServers
(:solr:solrj)
Test history:
https://develocity.apache.org/scans/tests?search.rootProjectNames=solr-root&tests.container=org.apache.solr.client.solrj.impl.LB2SolrClientTest&tests.test=testTwoServers
http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.client.solrj.impl.LB2SolrClientTest.testTwoServers
Test output:
/tmp/src/solr/solr/solrj/build/test-results/test/outputs/OUTPUT-org.apache.solr.client.solrj.impl.LB2SolrClientTest.txt
Reproduce with: ./gradlew :solr:solrj:test --tests
"org.apache.solr.client.solrj.impl.LB2SolrClientTest.testTwoServers"
"-Ptests.jvmargs=-XX:TieredStopAtLevel=1
-XX:+UseParallelGC -XX:ActiveProcessorCount=1
-XX:ReservedCodeCacheSize=120m" -Ptests.seed=BFC8AC5F327E55CE
-Ptests.timeoutSuite=600000! -Ptests.useSecurityManager=true
-Ptests.file.encoding=US-ASCII
```
The failure did not reproduce locally even after beasting, which makes it
likely to be a timing issue which may be more visible on the ultra-fast Crave
hardware. The failure was analyzed by an AI and a possible fix (though not
proven) is to add a small sleep between observing the new Jetty starting up
(being added to liveNodes) and actually sending requests to it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
