[
https://issues.apache.org/jira/browse/MAPREDUCE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748653#action_12748653
]
Hadoop QA commented on MAPREDUCE-918:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12417852/MAPREDUCE-918.patch
against trunk revision 808650.
+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 does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/531/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/531/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/531/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/531/console
This message is automatically generated.
> Test hsqldb server should be memory-only.
> -----------------------------------------
>
> Key: MAPREDUCE-918
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-918
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-918.patch
>
>
> Sqoop launches a standalone hsqldb server for unit tests, but it currently
> writes its database to disk and uses a connect string of {{//localhost}}. If
> multiple test instances are running concurrently, one test server may serve
> to the other instance of the unit tests, causing race conditions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
