You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Iliev Andrei (JIRA)" <ji...@apache.org> on 2009/11/16 16:55:39 UTC
[jira] Created: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
src\Test\Index\TestStressIndexing2.cs
-------------------------------------
Key: LUCENENET-260
URL: https://issues.apache.org/jira/browse/LUCENENET-260
Project: Lucene.Net
Issue Type: Bug
Reporter: Iliev Andrei
Dead lock issues and LUCENENET-143.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Michael Garski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780363#action_12780363 ]
Michael Garski commented on LUCENENET-260:
------------------------------------------
I just checked out the patch, and while it is concerning that for some reason the Java version runs without an issue, I'm not sure what we can do. I don't have a heavy background in Java, however Doug does and if he was not able to determine what the issue is I don't hold out much hope for finding it myself :)
Another thing I noticed is that about 1/3 of the time when running all of tests in TestStressIndexing2 TestRandomIWReader fails. When running it independently it never fails. There are no SetUp/TearDown issues as no such methods exist in the test and all variables are locally created (not instance fields). I'm not sure if this is a problem or not, just wanted to bring it up to see if anyone else sees the same thing with this patch.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Andrei Iliev
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy reassigned LUCENENET-260:
------------------------------
Assignee: Digy
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Michael Garski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780365#action_12780365 ]
Michael Garski commented on LUCENENET-260:
------------------------------------------
After fiddling with the settings on TestDriven.NET (VS add-in for NUnit testing) to not cache the test process between runs, all tests pass consistently now. Appears to be one of those issues that originate between the chair and keyboard over here.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Andrei Iliev
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Michael Garski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779091#action_12779091 ]
Michael Garski commented on LUCENENET-260:
------------------------------------------
I agree with Digy - if merely commenting out the test makes it pass, it could mask an underlying issue that is not being properly exercised and thus would pose an issue at run time.
I'll check out the patch and the tests today and post anything I find.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779136#action_12779136 ]
Digy commented on LUCENENET-260:
--------------------------------
Yes I have read that discussion, and I was the one who discussed it with Doug.
But the question is still there, why Lucene.Java doesn't fail but Lucene.NET does?
DIGY.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (LUCENENET-260) src\Test\Index\TestStressIndexing2.cs
Posted by "xzxz@mail.ru" <xz...@mail.ru>.
I guess it is due to the difference in sort algorithm(?). Anyway,
sorting in indexSerial has not to be done because it can (and it was)
changes the order of the fields added to the document.
Andrei.
Digy (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779047#action_12779047 ]
>
> Digy commented on LUCENENET-260:
> --------------------------------
>
> The problem with this issue is that although Lucene.Java uses also "Collections.sort(fields, fieldNameComparator)" in "indexSerial"
> this test fails only in Lucene.NET. What makes this difference?
>
> DIGY
>
>
>> src\Test\Index\TestStressIndexing2.cs
>> -------------------------------------
>>
>> Key: LUCENENET-260
>> URL: https://issues.apache.org/jira/browse/LUCENENET-260
>> Project: Lucene.Net
>> Issue Type: Bug
>> Reporter: Iliev Andrei
>> Assignee: Digy
>> Attachments: TestStressIndexing2.patch
>>
>>
>> Dead lock issues and LUCENENET-143.
>> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
>>
>
>
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779047#action_12779047 ]
Digy commented on LUCENENET-260:
--------------------------------
The problem with this issue is that although Lucene.Java uses also "Collections.sort(fields, fieldNameComparator)" in "indexSerial"
this test fails only in Lucene.NET. What makes this difference?
DIGY
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iliev Andrei updated LUCENENET-260:
-----------------------------------
Attachment: TestStressIndexing2.patch
New patch. Dead lock issue resolved in LUCENENET-255. So i remove this issue from the pacth.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy resolved LUCENENET-260.
----------------------------
Resolution: Fixed
I committed the patch with same "{{Lucene.Net-2.9.1}}" comment to mark the difference between Java & .Net
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Andrei Iliev
> Assignee: Digy
> Attachments: TestStressIndexing2.patch, TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779064#action_12779064 ]
Digy commented on LUCENENET-260:
--------------------------------
BTW, just commenting out the line 282
"SupportClass.CollectionsHelper.Sort(fields, fieldNameComparator)"
fixes all tests.
but is this correct?
DIGY
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iliev Andrei updated LUCENENET-260:
-----------------------------------
Attachment: TestStressIndexing2.patch
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iliev Andrei updated LUCENENET-260:
-----------------------------------
Description:
Dead lock issues and LUCENENET-143.
Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
was:Dead lock issues and LUCENENET-143.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy updated LUCENENET-260:
---------------------------
Attachment: TestStressIndexing2.patch
I give up seeking the reason for the difference between Lucene.Net & Lucene.Java.
If no objections, I will apply the patch which just comments out the sorting of "fields".
DIGY
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Andrei Iliev
> Assignee: Digy
> Attachments: TestStressIndexing2.patch, TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783687#action_12783687 ]
Digy edited comment on LUCENENET-260 at 11/30/09 3:11 PM:
----------------------------------------------------------
I give up seeking the reason for the difference between Lucene.Net & Lucene.Java.
If no objections, I will apply the patch which just comments out the sorting of "fields" (as in previous versions of Lucene.Net).
DIGY
was (Author: digydigy):
I give up seeking the reason for the difference between Lucene.Net & Lucene.Java.
If no objections, I will apply the patch which just comments out the sorting of "fields".
DIGY
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Andrei Iliev
> Assignee: Digy
> Attachments: TestStressIndexing2.patch, TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779125#action_12779125 ]
Iliev Andrei commented on LUCENENET-260:
----------------------------------------
Are you read discussion on LUCENENET-143?
<CITE>
Doug Sale added a comment - 01/Oct/08 04:13 PM Resolves outstanding issues. Incorporates fixes from earlier "TestStressIndexing2.patch" patches. These tests create docs composed of random fields and add them to an index. The index documents are then copied, field-by-field to another index. The indexes are then compared for equality. (This is all done with multiple threads and myriad different knobs twisted this way and that...) In the Java code, there were "random" orderings of the fields, which were sometimes sorted at different points depending on chance. However, the randomizations in the Java code are providing the completely consistent results, as the logic of the original tests could not work otherwise. The fixes incorporated in this patch include (introduced prior):
* a fix to the random ordering of the fields (not ported properly)
* a fix to the IComparator to ensure that fields are ordered by name and value (otherwise, fields with the same values were in an undefined order)
The recent fix
* removing the field sort when copying from original doc to new doc (when multiple fields of the same name exist in a doc, changing their order of addition changes the term position and offsets, causing the tests to fail)
</cite>
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iliev Andrei updated LUCENENET-260:
-----------------------------------
Attachment: (was: TestStressIndexing2.patch)
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779073#action_12779073 ]
Digy commented on LUCENENET-260:
--------------------------------
If the difference were due to the sort algorithm, then not sorting in Lucene.NET would cause a worse result.
DIGY
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-260)
src\Test\Index\TestStressIndexing2.cs
Posted by "Iliev Andrei (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779057#action_12779057 ]
Iliev Andrei commented on LUCENENET-260:
----------------------------------------
I guess it is due to the difference in sort algorithm(?). Anyway, sorting in indexSerial has not to be done because it can (and it was) changes the order of the fields added to the document.
> src\Test\Index\TestStressIndexing2.cs
> -------------------------------------
>
> Key: LUCENENET-260
> URL: https://issues.apache.org/jira/browse/LUCENENET-260
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Iliev Andrei
> Assignee: Digy
> Attachments: TestStressIndexing2.patch
>
>
> Dead lock issues and LUCENENET-143.
> Upd: Dead lock has been resolve in LUCENENET-255. So I update the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.