hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11617) Several tests are not stable (on OpenJDK / x86_64 / RHEL 7.1)
Date Wed, 25 Feb 2015 21:08:05 GMT

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

Steve Loughran commented on HADOOP-11617:
-----------------------------------------

Allen, we test on openjdk 7; though on RHEL6.x not 7.1. So this matters.

Tony: can you replicate these problems on hadoop-trunk? As that's where all fixes to things
like test stability are going to go, with backporting as and when appropriate. I doubt anybody
is going to worry about an unstable test on 2.4.x, on the basis that the problems may already
have been fixed. 

You can also have a search for JIRAs with the names in the test to see if they have been reported
and fixed already.

> Several tests are not stable (on OpenJDK / x86_64 / RHEL 7.1)
> -------------------------------------------------------------
>
>                 Key: HADOOP-11617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11617
>             Project: Hadoop Common
>          Issue Type: Bug
>         Environment: RHEL 7.1 / x86_64
>            Reporter: Tony Reix
>
> I'm now porting Hadoop 2.4.1 on PPC64 HW.
> In order to have an idea about the stability of the tests, I've run several times all
Hadoop tests in a RHEL 7.1 / x86_64 / OpenJDK environment.
> I've run it 12 times, for now, on the EXACT same environment.
> Using some tool, I have extracted the list of tests that do not always produce the same
results, listed below, showing some test unstability.
> I 'm now doing the same for version 2.6.0 on OpenJDK/Ubuntu/x86_64.
> Report gives:
> test-name N: T F E S |
> where:
> - N is the number of the test log file
> - and:
> T: Tests run
> F: Failure
> E: Error
> S: Skipped
> As an example (see below for full data):
> hdfs.server.datanode.TestDeleteBlockPool                      0:    2   0   0   0 |
> ........
> hdfs.server.datanode.TestDeleteBlockPool                      4:    2   0   1   0 |
> ........
> hdfs.server.datanode.TestDeleteBlockPool                     11:    2   0   0   0 |
> means that this test, out of 12 runs, had an error once, with 0 Failure and 0 Skipped
test.



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

Mime
View raw message