[
https://issues.apache.org/jira/browse/LUCENE-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046959#comment-14046959
]
Dawid Weiss commented on LUCENE-5786:
-------------------------------------
I've temporarily disabled ALL active configurations on freebsd jenkins. That
is, the following:
- Lucene-Solr-NightlyTests-trunk
- Lucene-Artifacts-trunk
- Lucene-Solr-Clover-4.x
- Lucene-Solr-Clover-trunk
- Lucene-Solr-Maven-4.x
- Lucene-Solr-Maven-trunk
- Lucene-Solr-NightlyTests-4.x
- Lucene-Artifacts-4.x
- Lucene-Solr-SmokeRelease-4.x
- Lucene-Solr-SmokeRelease-trunk
- Lucene-Solr-Tests-4.x-Java7
- Lucene-Solr-Tests-trunk-Java7
- Solr-Artifacts-4.x
- Solr-Artifacts-trunk
Most of these didn't have a successful run in what seems like months, so I
don't think it's a big problem. Still digging what's causing the death of the
test thread (apart from socket interrupt issue we know about there's still
something odd about those tests on freebsd).
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
