You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/12/14 21:46:13 UTC

[jira] [Updated] (HADOOP-11362) Test org.apache.hadoop.crypto.random.TestOsSecureRandom.testOsSecureRandomSetConf timing out

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

Steve Loughran updated HADOOP-11362:
------------------------------------
    Environment: ASF Jenkins, Java 7 & 8  (was: ASF Jenkins, Java 8)

> Test org.apache.hadoop.crypto.random.TestOsSecureRandom.testOsSecureRandomSetConf timing out
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11362
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11362
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0
>         Environment: ASF Jenkins, Java 7 & 8
>            Reporter: Steve Loughran
>
> The test {{org.apache.hadoop.crypto.random.TestOsSecureRandom.testOsSecureRandomSetConf}} is timing out on jenkins + Java 8.
> This is probably the exec() operation. It may be transient, it may be a java 8 + shell problem. 
> do we actually need this test in its present form? If a test for file handle leakage is really needed, attempting to create 64K instances of the OSRandom object should do it without having to resort to some printing and manual debugging of logs.



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