I was able to repro locally and track this down to an invalid test
assumption that incorrectly relies on doc ordering. We can relax some of
the randomness in the test case to ensure the doc ordering, but I think the
right thing to do is to relax the test assertions instead. The failing
assertion
Shoot, looking into this. This is a new test I added a month ago in
GH#12640. Not sure if we hit a random bug in the test or if the bug fix I
made in that change was incomplete somehow and this uncovered it.
Cheers,
-Greg
On Mon, Dec 11, 2023 at 11:17 AM Apache Jenkins Server <
Just a quick update on this...
> On 9 Dec 2023, at 09:09, Chris Hegarty wrote:
>
> Hi,
>
> We’ve encounter two very serious issues with the recent Lucene 9.9.0 release,
> both of which (even if taken by themselves) would warrant a 9.9.1. The issues
> are:
>
> 1.
Woops, sorry for suggesting this change in the first place! I didn't know
we had this validation for points, but not for postings.
On Fri, Dec 8, 2023 at 2:16 PM Michael McCandless
wrote:
> OK I reverted the "optimization" to not pull FieldInfo for a field when
> getting Points values from
