lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5786) Unflushed/ truncated events file (hung testing subprocess)
Date Tue, 01 Jul 2014 12:01:29 GMT

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

ASF subversion and git services commented on LUCENE-5786:
---------------------------------------------------------

Commit 1607058 from [~dawidweiss] in branch 'dev/trunk'
[ https://svn.apache.org/r1607058 ]

LUCENE-5786: Unflushed/ truncated events file (hung testing subprocess). Updating RR to 2.1.6

> Unflushed/ truncated events file (hung testing subprocess)
> ----------------------------------------------------------
>
>                 Key: LUCENE-5786
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5786
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/test
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>             Fix For: 5.0, 4.10
>
>
> This has happened several times on Jenkins, typically on SSLMigrationTest.testDistribSearch,
but probably on other tests as well.
> The symptom is: the test framework never terminates, it also reports an incorrect (?)
hung test.
> The problem is that the actual forked JVM is hung on reading stdin, waiting for the next
test suite (no test thread is present); the master process is hung on receiving data from
the forked jvm (both the events file and stdout spill is truncated in the middle of a test).
The last output is:
> {code}
> [
>   "APPEND_STDERR",
>   {
>     "chunk": "612639 T30203 oasu.DefaultSolrCoreState.doRecovery Running recovery - first
canceling any ongoing recovery%0A"
>   }
> ]
> [
>   "APPEND_STDERR"
> {code}
> Overall, it looks insane -- there are flushes after each test completes (normally or
not), there are tests *following* the one that last reported output and before dynamic suites
on stdin. 
> I have no idea. The best explanation is insane -- looks like the test thread just died
in the middle of executing Java code...



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

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


Mime
View raw message