> You don't really have to figure out exactly what the combinations are,
> just execute the test with the "reproduce with" flags set, cut/paste
> the error message at the root of your local Solr source tree in a
> command prompt.
> ant test -Dtestcase=CommitsImplTest
> -Dtests.method=testGetSegme
It looks to me as if this test is asserting that the segment in an index it
just created has some attributes, but in fact it does not. Perhaps there is
a codec that does not store any attributes with its segments, and Luke does
not expect this, and maybe the codec is being selected randomly by the
Here's a seed that fails for me consistently in IntelliJ:
"FEF692F43FE50191:656E22441676701C" running CommitsImplTest. Warning: I
have a bunch of local changes that might have perturbed the randomness so
possibly it might not reproduce for others. I just run the tests, open the
"Edit Configuration
bq. My understanding at this point is (though it may be a repeat of your words,)
first we should find out the combinations behind the failures.
If there are any particular patterns, there could be bugs, so we should fix
it.
You don't really have to figure out exactly what the combinations are,
jus
Can I ask one more question.
4> If MIke's intuition that it's one of the file system randomizations
that occasionally gets hit _and_ you determine that that's an invalid
test case (and for Luke requiring that the FS-basesd tests are all
that are necessary may be fine) I'm pretty sure you you can d
Thanks for your kind explanations,
sorry of course I know what is the randomization seed,
but your description and instruction is exactly what I wanted.
> The randomization can cause different
> combinations of "stuff" to happen. Say the locale is randomized to
> Turkish and a token is also rando
