[
https://issues.apache.org/jira/browse/SOLR-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062005#comment-18062005
]
David Smiley commented on SOLR-18142:
-------------------------------------
I can fairly easily reproduce this by telling IntelliJ to run this test with
JUnit in a loop until it errors. It only takes maybe 10 seconds, if that.
It appears this is a real bug, not a test bug. A race condition in which the
state didn't update when it should have.
> Flaky: CloudSolrClientCacheTest.testStaleStateRetryWaitsAfterSkipFailure
> ------------------------------------------------------------------------
>
> Key: SOLR-18142
> URL: https://issues.apache.org/jira/browse/SOLR-18142
> Project: Solr
> Issue Type: Test
> Components: SolrJ
> Affects Versions: 9.10
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
>
> This test has been failing since early December 2025.
> org.apache.solr.client.solrj.impl.CloudSolrClientCacheTest#testStaleStateRetryWaitsAfterSkipFailure
> [fucit.org|http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.client.solrj.impl.CloudSolrClientCacheTest.testStaleStateRetryWaitsAfterSkipFailure]
> and
> [develocity|https://develocity.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=solr-root&search.timeZoneId=America%2FNew_York&tests.container=org.apache.solr.client.solrj.impl.CloudSolrClientCacheTest&tests.test=testStaleStateRetryWaitsAfterSkipFailure]
> java.lang.AssertionError: Refresh should have been called
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]