You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/30 23:41:50 UTC
[jira] Created: (DERBY-4132) intermittent test failure: extra lock
in store/updatelocksJDBC30
intermittent test failure: extra lock in store/updatelocksJDBC30
----------------------------------------------------------------
Key: DERBY-4132
URL: https://issues.apache.org/jira/browse/DERBY-4132
Project: Derby
Issue Type: Bug
Components: Regression Test Failure
Affects Versions: 10.5.1.0
Reporter: Myrna van Lunteren
Test failure with 10.5 revision 757599 - passed on rerun:
********* Diff file derbyall/encryptionAll/storemats/storemats/updatelocksJDBC30
.diff
*** Start: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:03:36 **
*
15594d15593
< APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
15595a15595
> APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
15602d15601
< APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
15603a15603
> APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
Test Failed.
*** End: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:04:05 **
This was the run as part of encryptionAll - it passed as part of normal storemats.
This was with ibm 1.5:
Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR
5a))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JI
T enabled)
J9VM - 20070420_12448_lHdSMR
JIT - 20070419_1806_r8
GC - 200704_19)
JCL - 20070725
There were no check-ins that could've cause this to pop up, and it's the only time I've seen this...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-4132) intermittent test failure: extra lock
in store/updatelocksJDBC30
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-4132.
-----------------------------------
Assignee: Mike Matrigali
Resolution: Duplicate
resolving as duplicate of DERBY-4211.
> intermittent test failure: extra lock in store/updatelocksJDBC30
> ----------------------------------------------------------------
>
> Key: DERBY-4132
> URL: https://issues.apache.org/jira/browse/DERBY-4132
> Project: Derby
> Issue Type: Bug
> Components: Test
> Reporter: Myrna van Lunteren
> Assignee: Mike Matrigali
>
> Test failure with 10.5 revision 757599 - passed on rerun:
> ********* Diff file derbyall/encryptionAll/storemats/storemats/updatelocksJDBC30
> .diff
> *** Start: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:03:36 **
> *
> 15594d15593
> < APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
> 15595a15595
> > APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
> 15602d15601
> < APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
> 15603a15603
> > APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:04:05 **
> This was the run as part of encryptionAll - it passed as part of normal storemats.
> This was with ibm 1.5:
> Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR
> 5a))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JI
> T enabled)
> J9VM - 20070420_12448_lHdSMR
> JIT - 20070419_1806_r8
> GC - 200704_19)
> JCL - 20070725
> There were no check-ins that could've cause this to pop up, and it's the only time I've seen this...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4132) intermittent test failure: extra
lock in store/updatelocksJDBC30
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705597#action_12705597 ]
Knut Anders Hatlen commented on DERBY-4132:
-------------------------------------------
Also failed in the latest tinderbox: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/771180-derbyall_diff.txt
My guess is that it's a similar problem to DERBY-861/DERBY-2947.
> intermittent test failure: extra lock in store/updatelocksJDBC30
> ----------------------------------------------------------------
>
> Key: DERBY-4132
> URL: https://issues.apache.org/jira/browse/DERBY-4132
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.5.1.0
> Reporter: Myrna van Lunteren
>
> Test failure with 10.5 revision 757599 - passed on rerun:
> ********* Diff file derbyall/encryptionAll/storemats/storemats/updatelocksJDBC30
> .diff
> *** Start: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:03:36 **
> *
> 15594d15593
> < APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
> 15595a15595
> > APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
> 15602d15601
> < APP |UserTran|ROW |1 |U |A |(2,6) |GRANT|ACTIVE
> 15603a15603
> > APP |UserTran|ROW |2 |U |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: updatelocksJDBC30 jdk1.5.0 storemats:storemats 2009-03-23 23:04:05 **
> This was the run as part of encryptionAll - it passed as part of normal storemats.
> This was with ibm 1.5:
> Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR
> 5a))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JI
> T enabled)
> J9VM - 20070420_12448_lHdSMR
> JIT - 20070419_1806_r8
> GC - 200704_19)
> JCL - 20070725
> There were no check-ins that could've cause this to pop up, and it's the only time I've seen this...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.