[
https://issues.apache.org/jira/browse/OOZIE-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861799#comment-13861799
]
Hadoop QA commented on OOZIE-1660:
----------------------------------
Testing JIRA OOZIE-1660
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
. Tests run: 1380
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/985/
> DB connection misconfig causes all or most unit tests to fail
> -------------------------------------------------------------
>
> Key: OOZIE-1660
> URL: https://issues.apache.org/jira/browse/OOZIE-1660
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Attachments: OOZIE-1660.patch
>
>
> OOZIE-1655 changed oozie-default’s
> {{oozie.service.JPAService.create.db.schema}} to match oozie-site by setting
> it to {{false}}. This caused all or most unit tests to either fail with
> errors containing "{{Cannot create PoolableConnectionFactory}}" or to get
> stuck. For the unit tests, we need to set the property to true so that it
> will create the database schema because we don't create it manually like
> during a regular deployment. This was only working before because
> oozie-default and oozie-site were not in-sync.
> I'm not sure why test-patch in OOZIE-1655 didn't catch this or why I had to
> clone into a new folder to reproduce this locally either. Perhaps we're not
> deleting the database when doing a {{mvn clean}}?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
