You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Digy (JIRA)" <ji...@apache.org> on 2008/11/19 23:41:44 UTC

[jira] Closed: (LUCENENET-95) Nunite test for Search.TestDisjunctionMaxQuery.TestBooleanOptionalWithTiebreaker

     [ https://issues.apache.org/jira/browse/LUCENENET-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Digy closed LUCENENET-95.
-------------------------

    Resolution: Won't Fix
      Assignee: Digy

I think, I was the only one getting failures for this issue. Now, (with 2.3.1) this Nunit test passes without any problem.
This issue was good for seeing the different behaviours of debug and release mode of c# compiler.

DIGY.

> Nunite test for Search.TestDisjunctionMaxQuery.TestBooleanOptionalWithTiebreaker
> --------------------------------------------------------------------------------
>
>                 Key: LUCENENET-95
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-95
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Digy
>            Assignee: Digy
>            Priority: Trivial
>         Attachments: TryThis.patch
>
>
> Changing the line in TestDisjunctionMaxQuery.cs
> from
>    public const float SCORE_COMP_THRESH = 0.0000f;
> to
>    public const float SCORE_COMP_THRESH = 0.00001f;
> solves the problem but i am not sure if an exact match is needed or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.