[
https://issues.apache.org/jira/browse/LUCENE-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315880#comment-15315880
]
Michael McCandless commented on LUCENE-7316:
--------------------------------------------
bq. The question in my mind is, what changed with your latest patch that might
cause this?
It's hard to say if that change caused this ... it's true if you revert the
change, this seed passes, but that patch shifts the seeds for this test, I
think, and so we can't be sure there's a causal connection, though there could
definitely be one!
Really all that the previous change (LUCENE-7312) did was to increase by a wee
bit the {{Geo3DUtil.DECODE}} constant.
> Geo3d test failure
> ------------------
>
> Key: LUCENE-7316
> URL: https://issues.apache.org/jira/browse/LUCENE-7316
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/spatial3d
> Affects Versions: master (7.0)
> Reporter: Karl Wright
> Assignee: Karl Wright
> Attachments: LUCENE-7316.patch
>
>
> Reproducible on master with:
> {code}
> ant test -Dtestcase=TestGeo3DPoint -Dtests.method=testGeo3DRelations
> -Dtests.seed=EEA08DD7FAE3C688 -Dtests.multiplier=2 -Dtests.slow=true
> -Dtests.directory=MMapDirectory -Dtests.locale=es
> -Dtests.timezone=America/Manaus -Dtests.asserts=true
> -Dtests.file.encoding=UTF-8
> {code}
> Note: I was initially unable to reproduce this, until I pulled up code that
> [~mikemccand] recently committed. It seems possible that encoding/decoding
> changes are triggering it. Of specific concern is the new way
> maximum/minimum decoded values are computed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
