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

Dawid Weiss updated LUCENE-5567:
--------------------------------

    Description: 
This is a chicken-and-egg problem between thread leak detection and failure 
detection rule. I have an idea how to fix this. It'd prevent cascading failures 
resulting from previous zombie thread errors, like this one:

http://builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/81259/consoleText

{code}
   [junit4] Tests with failures:
   [junit4]   - 
org.apache.lucene.codecs.lucene45.TestLucene45DocValuesFormat.testSortedSetVariableLengthVsUninvertedField
   [junit4]   - org.apache.lucene.codecs.lucene45.TestLucene45DocValuesFormat 
(suite)
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestFailOnFieldCacheInsanity.testFailOnFieldCacheInsanity
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantBeforeClass
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantAfterClass
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantInTestMethod
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testNonStringProperties
   [junit4]   - 
org.apache.lucene.util.junitcompat.TestLeaveFilesIfTestFails.testLeaveFilesIfTestFails
{code}

  was:
This is a chicken-and-egg problem between thread leak detection and failure 
detection rule. I have an idea how to fix this. It'd prevent cascading failures 
resulting from previous zombie thread errors, like this one:

http://builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/81259/consoleText



> When a suite fails with zombie threads failure marker and count is not 
> propagated properly
> ------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-5567
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5567
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Minor
>
> This is a chicken-and-egg problem between thread leak detection and failure 
> detection rule. I have an idea how to fix this. It'd prevent cascading 
> failures resulting from previous zombie thread errors, like this one:
> http://builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/81259/consoleText
> {code}
>    [junit4] Tests with failures:
>    [junit4]   - 
> org.apache.lucene.codecs.lucene45.TestLucene45DocValuesFormat.testSortedSetVariableLengthVsUninvertedField
>    [junit4]   - org.apache.lucene.codecs.lucene45.TestLucene45DocValuesFormat 
> (suite)
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestFailOnFieldCacheInsanity.testFailOnFieldCacheInsanity
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantBeforeClass
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantAfterClass
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testRuleInvariantInTestMethod
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestSystemPropertiesInvariantRule.testNonStringProperties
>    [junit4]   - 
> org.apache.lucene.util.junitcompat.TestLeaveFilesIfTestFails.testLeaveFilesIfTestFails
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to