[
https://issues.apache.org/jira/browse/STORM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531439#comment-14531439
]
ASF GitHub Bot commented on STORM-811:
--------------------------------------
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/547
STORM-811: remove old metastor_db before running tests again.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-811
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/547.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #547
----
commit e40a0fe1b7d52b5f8ad2b9b08d9884dba4829d13
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-05-06T21:17:08Z
STORM-811: remove old metastor_db before running tests again.
----
> Hive test fail after first run
> ------------------------------
>
> Key: STORM-811
> URL: https://issues.apache.org/jira/browse/STORM-811
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> I don't know why but on my Mac, not on Linux, or on other peoples Mac's.
> leaving the derby metastor db on the file system results in the tests failing
> the second time with an array index out of bounds error as captured by
> derby.log.
> I can work around this by cleaning out the DB state before running the tests.
> I really don't know why, but it is 100% reproducible, but just for me :).
> So updating the build to clean it up before the tests run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
