You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2023/01/19 20:31:12 UTC

[GitHub] [lucene] vigyasharma opened a new pull request, #12098: Fix failure in TestIndexSortSortedNumericDocValuesRangeQuery

vigyasharma opened a new pull request, #12098:
URL: https://github.com/apache/lucene/pull/12098

   Fixes bug in `TestIndexSortSortedNumericDocValuesRangeQuery. testCountBoundary`. 
   Addresses #12097 
   


-- 
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: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


[GitHub] [lucene] vigyasharma merged pull request #12098: Fix failure in TestIndexSortSortedNumericDocValuesRangeQuery

Posted by GitBox <gi...@apache.org>.
vigyasharma merged PR #12098:
URL: https://github.com/apache/lucene/pull/12098


-- 
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: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


[GitHub] [lucene] rmuir commented on pull request #12098: Fix failure in TestIndexSortSortedNumericDocValuesRangeQuery

Posted by GitBox <gi...@apache.org>.
rmuir commented on PR #12098:
URL: https://github.com/apache/lucene/pull/12098#issuecomment-1397749519

   if a test wants to enforce it only has one segment, it should `forceMerge()`, make use of `LuceneTestCase.getOnlyLeafReader()`, etc. 
   
   Otherwise the number of segments can vary based on flushing/merging, especially when using `LuceneTestCase.newIndexWriterConfig()`, `RandomIndexWriter`, etc. so in general, we want to avoid assertions that rely upon certain segment structure.


-- 
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: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org