[jira] [Commented] (LUCENE-6478) Test execution can hang with java.security.debug

["Dawid Weiss (JIRA)" <ji...@apache.org>]

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

Dawid Weiss commented on LUCENE-6478:
-------------------------------------

Good news, Robert ([~rcmuir]). I think I fixed it in the RR -- I was successfull at running tests with full security policy dump.
{code}
cd lucene
ant test-core -Dtests.useSecurityManager=true  "-Dtests.class=*FuzzyTermOnShortTermsTest*" -Dtests.seed=deadbeef -Dtests.jvms=1 -Dtests.verbose=true -Dargs="-Djava.security.debug=all"
{code}
You need {{-Dtests.verbose}} -- there's tons of output from policy debug and it max sysout limit rule complains otherwise. I attach a patch that I used against trunk. Note *it uses a snapshot version of RR*, you need to fetch it from sonatype snapshots repo (or install it manually in your {{.m2}}).

> Test execution can hang with java.security.debug
> ------------------------------------------------
>
>                 Key: LUCENE-6478
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6478
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>
> As reported by Robert:
> {code}
> # clone trunk
> cd lucene/core/
> ant test -Dargs="-Djava.security.debug=access:failure" -Dtestcase=TestDemo
> {code}
> Hangs the test runner. The same problem appears to be present in ES builds too. It seems like some kind of weird stream buffer problem, the security framework seems to be writing to the native descriptors directly. Will have to dig (deep...).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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