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

[jira] [Created] (HBASE-6918) Debugging to help figure what is different up on jenkins when TestHeapSize runs

stack created HBASE-6918:
----------------------------

             Summary: Debugging to help figure what is different up on jenkins when TestHeapSize runs
                 Key: HBASE-6918
                 URL: https://issues.apache.org/jira/browse/HBASE-6918
             Project: HBase
          Issue Type: Bug
          Components: test
    Affects Versions: 0.96.0
            Reporter: stack
            Assignee: stack


TestHeapSize will pass locally then fail up on jenkins.  Add debugging to the test that prints detail on environment and jvm in particular to can figure what is different between two environments (it used to be that the d32 flag was needed to mimic jenkins but now we are jdk7, the d32 flag doesn't work w/ my oracle jvm... let me see what jenkins has).

--
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] [Resolved] (HBASE-6918) Debugging to help figure what is different up on jenkins when TestHeapSize runs

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

stack resolved HBASE-6918.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.0

Committed to trunk.  Lets see what it turns up.
                
> Debugging to help figure what is different up on jenkins when TestHeapSize runs
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-6918
>                 URL: https://issues.apache.org/jira/browse/HBASE-6918
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.96.0
>
>         Attachments: 6918.txt
>
>
> TestHeapSize will pass locally then fail up on jenkins.  Add debugging to the test that prints detail on environment and jvm in particular to can figure what is different between two environments (it used to be that the d32 flag was needed to mimic jenkins but now we are jdk7, the d32 flag doesn't work w/ my oracle jvm... let me see what jenkins has).

--
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-6918) Debugging to help figure what is different up on jenkins when TestHeapSize runs

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

stack updated HBASE-6918:
-------------------------

    Attachment: 6918.txt

What I committed.
                
> Debugging to help figure what is different up on jenkins when TestHeapSize runs
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-6918
>                 URL: https://issues.apache.org/jira/browse/HBASE-6918
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.96.0
>
>         Attachments: 6918.txt
>
>
> TestHeapSize will pass locally then fail up on jenkins.  Add debugging to the test that prints detail on environment and jvm in particular to can figure what is different between two environments (it used to be that the d32 flag was needed to mimic jenkins but now we are jdk7, the d32 flag doesn't work w/ my oracle jvm... let me see what jenkins has).

--
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-6918) Debugging to help figure what is different up on jenkins when TestHeapSize runs

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

Hudson commented on HBASE-6918:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #203 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/203/])
    HBASE-6918 Debugging to help figure what is different up on jenkins when TestHeapSize runs (Revision 1392753)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java

                
> Debugging to help figure what is different up on jenkins when TestHeapSize runs
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-6918
>                 URL: https://issues.apache.org/jira/browse/HBASE-6918
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.96.0
>
>         Attachments: 6918.txt
>
>
> TestHeapSize will pass locally then fail up on jenkins.  Add debugging to the test that prints detail on environment and jvm in particular to can figure what is different between two environments (it used to be that the d32 flag was needed to mimic jenkins but now we are jdk7, the d32 flag doesn't work w/ my oracle jvm... let me see what jenkins has).

--
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-6918) Debugging to help figure what is different up on jenkins when TestHeapSize runs

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

Hudson commented on HBASE-6918:
-------------------------------

Integrated in HBase-TRUNK #3404 (See [https://builds.apache.org/job/HBase-TRUNK/3404/])
    HBASE-6918 Debugging to help figure what is different up on jenkins when TestHeapSize runs (Revision 1392753)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java

                
> Debugging to help figure what is different up on jenkins when TestHeapSize runs
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-6918
>                 URL: https://issues.apache.org/jira/browse/HBASE-6918
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.96.0
>
>         Attachments: 6918.txt
>
>
> TestHeapSize will pass locally then fail up on jenkins.  Add debugging to the test that prints detail on environment and jvm in particular to can figure what is different between two environments (it used to be that the d32 flag was needed to mimic jenkins but now we are jdk7, the d32 flag doesn't work w/ my oracle jvm... let me see what jenkins has).

--
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