[
https://issues.apache.org/jira/browse/DERBY-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252037#comment-13252037
]
Myrna van Lunteren commented on DERBY-5671:
-------------------------------------------
Thanks Rick.
I've been running nstest with sane tests in a small configuration (passing in
'Embedded small' - 10x at each 'run'/build) and that seems to be much more
manageable than before the backing out.
I am now running the same small configuration with insane jars, and things look
ok there too.
I will confirm a 'full' nstest run after that. Theoretically I would let it run
for 2 weeks' (or until some security-minded person/tool boots the machine to
install windows security fixes from under me).
> NsTest does not run on trunk do multiple issues stemming from concurrency
> improvements
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-5671
> URL: https://issues.apache.org/jira/browse/DERBY-5671
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Reporter: Kathey Marsden
> Priority: Critical
>
> As I understand it at least since September 30 of last year, the system test
> NsTest has been broken on trunk. In these six months the test has not been
> runnable, so we do not know if new issues have been introduced with sequence
> generators or most importantly with auto-increment columns that are now based
> on them, which many, many applications rely upon. Even if the known
> problems are fixed later in the 10.9 release cycle and new problems are
> exposed, we won't be able to go back to any point in time to discover when
> they might be released.
> In 10.8 we coped with this problem by backing out the concurrency
> improvements (DERBY-5448) pending fixes for DERBY-5422, DERBY-5454,
> DERBY-5430. Currently none of those issues have been assigned. Since this
> has been going on now for six months, I think we urgently need to stabiliize
> auto-increment columns and get this test running again on trunk. I can see
> three possible options.
> 1) Someone with interest assign themselves to these issues and make
> significant progress over the next few weeks.
> 2) Make the concurrency improvements optional with a property which
> defaults to false (I don't know if this is practical)
> 3) Back the concurrency performance improvements out of trunk until these
> issues have been resolved and the change can be resubmitted.
> I realize that NsTest is not the easiest test to work with but it does seem
> to have found serious problems with generated columns that I think users are
> likely to hit. In the past, a similiar disregard for mailjdbc exposing a
> corruption issue meant that we actually released a bad corruption issue that
> I know hit many users of Derby before we addressed it. Autoincrement is
> widely, widely, used. We need to get it stabilized and the test running on
> trunk. Although the system tests are not particularly easy to deal with,
> they are all we have and they do find issues.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
