[
https://issues.apache.org/jira/browse/DERBY-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6676:
---------------------------------
Attachment: derby-6676-01-aa-singleUseDecorator.diff
Attaching derby-6676-01-aa-singleUseDecorator.diff. This patch eliminates the
dblook warning when I run the full regression tests.
The warning did not appear when I ran Test_6661 standalone. When I added debug
diagnostics and ran the complete suite, it appeared that the warning was being
raised because the database was not empty to start out with. It had jar files
in it whose sources outside the database had been cleaned up already. The jar
files weren't found when Test_6661 created a dblook script and tried to run it.
The fix is to make Test_6661 use its own, empty, single-use database.
Touches the following file:
M
java/testing/org/apache/derbyTesting/functionTests/tests/tools/Test_6661.java
> dblook warning printed on std err during nightly test runs
> ----------------------------------------------------------
>
> Key: DERBY-6676
> URL: https://issues.apache.org/jira/browse/DERBY-6676
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Attachments: derby-6676-01-aa-singleUseDecorator.diff
>
>
> I see the following error printed to stderr during the nightly tests (nn):
> {noformat}
> stderr
> -- Note: At least one unexpected error/warning message was
> -- encountered during DDL generation. See dblook.log
> -- to review the message(s).
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
