[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258323#comment-13258323 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523507/5831.remove.all.mapreduce.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 26 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1592//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1592//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1592//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt, > 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258066#comment-13258066 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523458/5831.remove.all.mapreduce.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 26 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.client.TestFromClientSide Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1591//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1591//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1591//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258035#comment-13258035 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523450/5831.remove.all.mapreduce.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 26 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestColumnSeeking Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1590//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1590//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1590//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt, > 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258019#comment-13258019 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523435/5831.remove.all.mapreduce.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 26 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1589//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1589//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1589//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258008#comment-13258008 ] stack commented on HBASE-5831: -- @Jon Hmm.. yes. You are right. Both times it passed. It was worth committing hbase-5794 then. Now to find the other hanging tests... > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257991#comment-13257991 ] Jonathan Hsieh commented on HBASE-5831: --- @Stack, it seems from the HBASE-5794 patch the mapreduce tests, including TestLoadIncrementalHFilesSplitRecovery, were passing. https://builds.apache.org/job/PreCommit-HBASE-Build/1587//testReport/org.apache.hadoop.hbase.mapreduce/ The other failures on HBASE-5794 seem somewhat odd however. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257925#comment-13257925 ] stack commented on HBASE-5831: -- Thanks Jon. I tried it over in HBASE-5794, setting it back down again, but it didn't seen to matter. I committed the patch there which undoes the 100 anyways since Mikhail said the change was good for some 0.89fb tests, he wasn't sure about trunk. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt, 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257916#comment-13257916 ] Jonathan Hsieh commented on HBASE-5831: --- I tried the tested in question on trunk and it passes in eclipse. It fails in mvn. I've encountered this kind of problem previously as well with HBASE-5793 -- my eclipse setup differs from mvn by not using ./src/test/resources/hbase-site.xml in the resources dir. Since the test expects and error, my guess is this may have to do with the client retry number getting bumped up to 100 in the resource hbase-site.xml file in HBASE-5747. When I edited that file back down client retries to 10 it passes in about 2 minutes. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257911#comment-13257911 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523418/5831.remove.all.mapreduce.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 26 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.constraint.TestConstraint org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithRemove Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1585//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1585//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1585//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.all.mapreduce.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257826#comment-13257826 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523399/5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1581//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1581//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1581//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257773#comment-13257773 ] stack commented on HBASE-5831: -- @Todd That'd be nice (smile) This test run did 936 tests which is more than normal. Let me try again. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257756#comment-13257756 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523387/5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.io.hfile.TestLruBlockCache Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1580//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1580//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1580//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257719#comment-13257719 ] Todd Lipcon commented on HBASE-5831: I agree, we should make it a requirement that all @Tests have a timeout and a category. The coolest would be a script that looked at the previous Jenkins results, and automatically generated a diff for all the tests, setting their timeouts to 2x the previous runtime, so we don't have to manually guess a timeout for all our hundreds of tests :) > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257701#comment-13257701 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523376/5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1579//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1579//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1579//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257647#comment-13257647 ] stack commented on HBASE-5831: -- @Todd We can do that and then require it. Nkeyway has a script for test categorizations. I've been talking w/ him about adding it to general build. We could expand it to require tests have timeouts too. Let me try this patch again. I want another clean run w/o a hang to be convinced this is the problem test. Need to too amend Ted's little script to look for tests that run 0 tests. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257626#comment-13257626 ] Todd Lipcon commented on HBASE-5831: Maybe adding a "timeout=6" or so to the test would let it properly get marked as failed without screwing the whole build? I've found that surefire really sucks at handling test timeouts unless they also have junit annotations with a timeout. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257615#comment-13257615 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523365/5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestSplitLogManager Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1575//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1575//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1575//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257595#comment-13257595 ] Zhihong Yu commented on HBASE-5831: --- With the following change, I was able to run the test 6 times without hanging JVM: {code} Index: src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java === --- src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java (revision 1327779) +++ src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java (working copy) @@ -220,7 +220,7 @@ * Test that shows that exception thrown from the RS side will result in an * exception on the LIHFile client. */ - @Test(expected=IOException.class) + // @Test(expected=IOException.class) public void testBulkLoadPhaseFailure() throws Exception { String table = "bulkLoadPhaseFailure"; setupTable(table, 10); {code} > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257587#comment-13257587 ] Zhihong Yu commented on HBASE-5831: --- I captured stack trace twice when the test was running and got similar result: {code} "main" prio=5 tid=102801000 nid=0x100601000 waiting on condition [1005fe000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <7854b0c00> (a java.util.concurrent.FutureTask$Sync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281) at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:218) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.bulkLoadPhase(LoadIncrementalHFiles.java:296) at org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:248) at org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testBulkLoadPhaseFailure(TestLoadIncrementalHFilesSplitRecovery.java:256) {code} Maybe disabling testBulkLoadPhaseFailure is enough for Jenkins to get back to normal. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, > 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257583#comment-13257583 ] Zhihong Yu commented on HBASE-5831: --- Interesting: TestLoadIncrementalHFilesSplitRecovery wasn't listed on trunk Jenkins build output. @Jonathan H: This test was introduced in HBASE-4552 and modified in HBASE-4740. Maybe you have some insight. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5831) hadoopqa builds not completing
[ https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257566#comment-13257566 ] Hadoop QA commented on HBASE-5831: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523359/5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1574//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1574//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1574//console This message is automatically generated. > hadoopqa builds not completing > -- > > Key: HBASE-5831 > URL: https://issues.apache.org/jira/browse/HBASE-5831 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Blocker > Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt > > > No test failures but build complains it has failed. trunk build seems to > have the same affliction: > {code} > Results : > Tests run: 909, Failures: 0, Errors: 0, Skipped: 9 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 41:19.273s > [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012 > [INFO] Final Memory: 59M/451M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -1 overall. Here are the results of testing the latest attachment > http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt > against trunk revision . > +1 @author. The patch does not contain any @author tags. > +1 tests included. The patch appears to include 3 new or modified tests. > +1 javadoc. The javadoc tool did not generate any warning messages. > +1 javac. The applied patch does not increase the total number of javac > compiler warnings. > -1 findbugs. The patch appears to introduce 6 new Findbugs (version > 1.3.9) warnings. > +1 release audit. The applied patch does not increase the total number > of release audit warnings. > -1 core tests. The patch failed these unit tests: > {code} > Its not apparent that any particular test is not finishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira