[ 
https://issues.apache.org/jira/browse/SOLR-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726411#comment-17726411
 ] 

Chris M. Hostetter commented on SOLR-16819:
-------------------------------------------

i think i understand what happened here ... working on a patch to test my 
hypothosis.

> (nightly) HttpPartitionTest  broken regardless of seed
> ------------------------------------------------------
>
>                 Key: SOLR-16819
>                 URL: https://issues.apache.org/jira/browse/SOLR-16819
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Priority: Major
>
> {{HttpPartitionTest}} (which is a nightly test) has been failing 100% of the 
> time on jenkins for the past month (2023-05-01 to 2023-05-25 at time of 
> writting)
> Before that – we have no reported failures since 2022-07, which is weird 
> because up to that point this test was always a bit flakey.
> Checking out older version of main from april and running {{./gradlew -p 
> solr/core test -Ptests.nightly=true --tests HttpPartitionTest}} show that 
> this test definitely *should* have failed a lot of nightly builds prior to 
> 2023-05-01 ... so i'm assuming we had some jenkins or gradle build glitch 
> that prevented it from being run? (i didn't dig into this)
> picking an arbitrary commit point from a few months ago when i could confirm 
> the test *did* pass i then ran {{git bisect}} and it identified 
> 708524315bf64ed5dbcfd470c8fadd435c861f78 / SOLR-10466 as the first bad commit 
> (which is also the most recent commit to this file)
>  
> (NOTE: this problem also seems to affect the subclass 
> {{HttpPartitionWithTlogReplicasTest}} which has also been failing 100% of the 
> time for the past month)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to