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

ASF subversion and git services commented on SOLR-15839:
--------------------------------------------------------

Commit 84a542cb4c275038e562384e5c01a2ea39894c07 in solr's branch 
refs/heads/main from Uwe Schindler
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=84a542c ]

SOLR-15839: Don't mock oal.search.Sort class (why the hell was this needed?) 
(#452)



> After upgrade of Lucene a test mocking org.apache.lucene.search.Sort no 
> longer works (final class)
> --------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-15839
>                 URL: https://issues.apache.org/jira/browse/SOLR-15839
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Tests
>    Affects Versions: main (9.0)
>            Reporter: Uwe Schindler
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> See error message: 
> https://jenkins.thetaphi.de/job/Solr-main-Linux/2070/testReport/junit/org.apache.solr.handler.component/QueryComponentPartialResultsTest/includesPartialShardResultWhenUsingExplicitScoreSort/
> {noformat}
> Mockito cannot mock/spy because :
>  - final class
>       at 
> __randomizedtesting.SeedInfo.seed([73F81B5CBD838FB3:99A391C7F33C98A3]:0)
>       at 
> app//org.apache.solr.handler.component.MockSortSpecBuilder.withSortFields(MockSortSpecBuilder.java:37)
>       at 
> app//org.apache.solr.handler.component.QueryComponentPartialResultsTest.includesPartialShardResultWhenUsingExplicitScoreSort(QueryComponentPartialResultsTest.java:54)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to