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 2013/09/03 21:23:51 UTC
[jira] [Commented] (DERBY-5630) intermittent test failure in
store/lockTableVTI.sql
[ https://issues.apache.org/jira/browse/DERBY-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756958#comment-13756958 ]
Myrna van Lunteren commented on DERBY-5630:
-------------------------------------------
Failed again: http://people.apache.org/~myrnavl/derby_test_results/v10_10/windows/testlog/weme6.2/1518442-suites.All_diff.txt
> intermittent test failure in store/lockTableVTI.sql
> ---------------------------------------------------
>
> Key: DERBY-5630
> URL: https://issues.apache.org/jira/browse/DERBY-5630
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.3.0, 10.10.1.3
> Environment: Windows 2008, ibm 1.6 SR9 FP1, ibm 1.4.2.
> Reporter: Myrna van Lunteren
> Labels: derby_triage10_10
>
> I've seen this test fail twice recently, once with ibm 1.6, once with 1.4.2, both times on the same machine (which is running 10.8 nightly testing):
> The diff is as follows:
> 51a52,61
> > ij(C1)> commit;
> > ij(C1)> call SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.locks.waitTimeout', '180');
> > 0 rows inserted/updated/deleted
> > ij(C1)> commit;
> > ij(C1)> set connection c2 ;
> > ij(C2)> wait for C2S1;
> > 3 rows inserted/updated/deleted
> > ij(C2)> select state from syscs_diag.lock_table order by state;
> > STATE
> > -----
> 53,63d62
> < WAIT
> < ij(C1)> commit;
> < ij(C1)> call SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.locks.waitTimeout', '180');
> < 0 rows inserted/updated/deleted
> < ij(C1)> commit;
> < ij(C1)> set connection c2 ;
> < ij(C2)> wait for C2S1;
> < 3 rows inserted/updated/deleted
> < ij(C2)> select state from syscs_diag.lock_table order by state;
> < STATE
> < -----
> 67d65
> < GRANT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira