You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2012/11/07 17:47:11 UTC

[jira] [Created] (HBASE-7113) TestGzipFilter is flaky

Jimmy Xiang created HBASE-7113:
----------------------------------

             Summary: TestGzipFilter is flaky
                 Key: HBASE-7113
                 URL: https://issues.apache.org/jira/browse/HBASE-7113
             Project: HBase
          Issue Type: Bug
          Components: test
            Reporter: Jimmy Xiang
            Assignee: Jimmy Xiang
            Priority: Minor


Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492514#comment-13492514 ] 

Jimmy Xiang commented on HBASE-7113:
------------------------------------

Thanks for reviewing it.  I updated the title to be clear.
                
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HBASE-7113:
-------------------------------

    Summary: TestGzipFilter is flaky with jdk1.7  (was: TestGzipFilter is flaky)
    
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492746#comment-13492746 ] 

Hudson commented on HBASE-7113:
-------------------------------

Integrated in HBase-TRUNK #3519 (See [https://builds.apache.org/job/HBase-TRUNK/3519/])
    HBASE-7113 TestGzipFilter is flaky with jdk1.7 (Revision 1406797)

     Result = FAILURE
jxiang : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestGzipFilter.java

                
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492558#comment-13492558 ] 

Hadoop QA commented on HBASE-7113:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12552490/trunk-7113.patch
  against trunk revision .

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

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

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 2.0 profile.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 87 warning messages.

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

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

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

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3254//console

This message is automatically generated.
                
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HBASE-7113:
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)
    
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492511#comment-13492511 ] 

Jimmy Xiang commented on HBASE-7113:
------------------------------------

Yes, that's right.  It is related to jdk7.
                
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7113) TestGzipFilter is flaky

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HBASE-7113:
-------------------------------

    Attachment: trunk-7113.patch
    
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492849#comment-13492849 ] 

Hudson commented on HBASE-7113:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #252 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/252/])
    HBASE-7113 TestGzipFilter is flaky with jdk1.7 (Revision 1406797)

     Result = FAILURE
jxiang : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestGzipFilter.java

                
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492508#comment-13492508 ] 

Andrew Purtell commented on HBASE-7113:
---------------------------------------

Ah, I see a patch was added. Is this a JDK7 thing?
                
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492512#comment-13492512 ] 

Andrew Purtell commented on HBASE-7113:
---------------------------------------

+1
                
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7113) TestGzipFilter is flaky with jdk1.7

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-7113:
----------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: HBASE-5261
    
> TestGzipFilter is flaky with jdk1.7
> -----------------------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7113) TestGzipFilter is flaky

Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HBASE-7113:
-------------------------------

    Status: Patch Available  (was: Open)

testScannerResultCodes must run after testGzipFilter. Since there is no good way to specify the execution order, I re-order the test code a little.
                
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7113) TestGzipFilter is flaky

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492504#comment-13492504 ] 

Andrew Purtell commented on HBASE-7113:
---------------------------------------

This is the first time I've seen this in at least a year. Flagging the test as flaky may be premature. Can we see more detail on the failure?
                
> TestGzipFilter is flaky
> -----------------------
>
>                 Key: HBASE-7113
>                 URL: https://issues.apache.org/jira/browse/HBASE-7113
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-7113.patch
>
>
> Failed tests:   testScannerResultCodes(org.apache.hadoop.hbase.rest.TestGzipFilter): expected:<204> but was:<200>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira