[ 
https://issues.apache.org/jira/browse/LUCENE-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454866#comment-16454866
 ] 

Karl Wright commented on LUCENE-8281:
-------------------------------------

I added a reverse assertion to the code which cross-checks the second test 
point against the first after its in-set-ness has been determined.  This 
assertion fails pretty regularly.  With the assertion in place, you can blow it 
up with the following already-existing test:

{code}
ant test  -Dtestcase=GeoPolygonTest -Dtests.method=testLUCENE8276_case1
{code}

The assertion code is pretty straightforward:

{code}
    assert isInSet(testPoint1.x, testPoint1.y, testPoint1.z,
      testPoint2,
      testPoint2InSet,
      testPoint2FixedXPlane, testPoint2FixedXAbovePlane, 
testPoint2FixedXBelowPlane,
      testPoint2FixedYPlane, testPoint2FixedYAbovePlane, 
testPoint2FixedYBelowPlane,
      testPoint2FixedZPlane, testPoint2FixedZAbovePlane, 
testPoint2FixedZBelowPlane) == testPoint1InSet : "Test point1 not correctly 
in/out of set according to test point2";
{code}

Debugging now to figure out why this doesn't reliably work.

> Random polygon test failures
> ----------------------------
>
>                 Key: LUCENE-8281
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8281
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/spatial3d
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Major
>         Attachments: LUCENE-8281.jpg
>
>
> Reproduce here:
> {code}
> ant test  -Dtestcase=RandomGeoPolygonTest 
> -Dtests.method=testCompareSmallPolygons -Dtests.seed=42573983280EE568 
> -Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=jmc-TZ 
> -Dtests.timezone=US/Alaska -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to