[
https://issues.apache.org/jira/browse/LUCENE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314080#comment-15314080
]
Michael McCandless commented on LUCENE-7312:
--------------------------------------------
bq. except for some debugging code
Woops, I'll remove.
bq. Basically, by adding the 0.5 right before floor time I made sure no such
effects could happen?
Hmm, I think you can still see these effects with this math, unfortunately.
Probably if you ported this new test case over the this Geo3DDVField's encoding
it would fail?
Floating point precision issues are a nightmare when you want tests to be
precise :)
> Geo3dPoint test failure
> -----------------------
>
> Key: LUCENE-7312
> URL: https://issues.apache.org/jira/browse/LUCENE-7312
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/spatial3d
> Affects Versions: master (7.0)
> Reporter: Karl Wright
> Assignee: Karl Wright
> Attachments: LUCENE-7312.patch
>
>
> Here's the failure:
> {code}
> ant test -Dtestcase=TestGeo3DPoint -Dtests.method=testEncodeDecodeRoundsDown
> -Dtests.seed=7046405B94C1716E -Dtests.multiplier=3 -Dtests.slow=true
> -Dtests.locale=da-DK -Dtests.timezone=America/Detroit -Dtests.asserts=true
> -Dtests.file.encoding=UTF-8
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
