[
https://issues.apache.org/jira/browse/SOLR-17139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812315#comment-17812315
]
Jason Gerlowski commented on SOLR-17139:
----------------------------------------
Can anyone confirm whether the failure reproduces for them with the gradle
command above? Would love to know whether the failure requires only the seed
to reproduce, or whether there's also a timing or environmental factor that
makes it reproducible in my local env.
> Fix reproducibly failing seed for PeerSyncWithLeaderTest
> --------------------------------------------------------
>
> Key: SOLR-17139
> URL: https://issues.apache.org/jira/browse/SOLR-17139
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Tests
> Affects Versions: main (10.0)
> Reporter: Jason Gerlowski
> Priority: Minor
>
> PeerSyncWithLeaderTest has been flaky for some time, failing somewhere
> between 1 and 5% of runs going as far back as 2018 according to fucit.
> Usually I'm unable to reproduce failures, but I found a seed this morning
> that fails (for me at least) 10 out of 10 times:
> {code}
> ./gradlew :solr:core:test --tests
> "org.apache.solr.update.PeerSyncWithLeaderTest.test" -Ptests.jvms=12
> "-Ptests.jvmargs=-XX:TieredStopAtLevel=1 -XX:+UseParallelGC
> -XX:ActiveProcessorCount=1 -XX:ReservedCodeCacheSize=120m"
> -Ptests.seed=53640FCB37714D82 -Ptests.file.encoding=US-ASCII
> {code}
> (Environment is Intel Xeon, MacOS Sonoma, Java 17)
> We should take this opportunity to fix the flakiness, while it's
> reproducible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
