Java DB testing and reporting infrastructure.
Error nightly 10.12 (rev 1704145)
There were execution errors and/or timeouts.
There were at least 2 failures.
[
https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905788#comment-14905788
]
Mike Matrigali commented on DERBY-6837:
---
derby was just not designed with concurrent
[
https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905784#comment-14905784
]
Mike Matrigali commented on DERBY-6837:
---
if you can not reproduce, please add to you
[
https://issues.apache.org/jira/browse/DERBY-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905553#comment-14905553
]
Rick Hillegas commented on DERBY-6836:
--
Thanks for verifying that, Martin.
> syscs_i
Moritz Bechler created DERBY-6838:
-
Summary: LookaheadSuccess in SQLParser leaks caller through
backtrace
Key: DERBY-6838
URL: https://issues.apache.org/jira/browse/DERBY-6838
Project: Derby
[
https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Yves LINET updated DERBY-6837:
---
Description:
When I add an index on new created table (software installation) I get ERROR
40X
Jean-Yves LINET created DERBY-6837:
--
Summary: ERROR 40XL1 due to incorrect lock
Key: DERBY-6837
URL: https://issues.apache.org/jira/browse/DERBY-6837
Project: Derby
Issue Type: Bug
