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

Hadoop QA commented on HADOOP-11362:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12687136/0001-HADOOP-11362-Test-org.apache.hadoop.crypto.random.Te.patch
  against trunk revision 25a0440.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 3 new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5266//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5266//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5266//console

This message is automatically generated.

> 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
>         Attachments: 
> 0001-HADOOP-11362-Test-org.apache.hadoop.crypto.random.Te.patch
>
>
> 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)

Reply via email to