db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-5630) intermittent test failure in store/lockTableVTI.sql
Date Mon, 10 Feb 2014 18:58:25 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-5630.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 11.0.0.0
                   10.10.1.4
                   10.9.2.2
                   10.8.3.3

I am closing this issue, I think it is now sufficiently addressed.
I noted a test failure with ibm 1.4.2 on the 10.8 branch after my check in, see: 
http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm142/1566493-suites.All_diff.txt

This test failure is in UpdateLocksTest.testReadUncommitted, and this test ran *before* the
test that I had added to the _Suite, so it can not be related. There have been other issues
with the UpdateLocksTest (see DERBY-5667, so I'm assuming it's a longer running instability
in UpdateLocksTest.

> 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.4
>         Environment: Windows 2008, ibm 1.6 SR9 FP1, ibm 1.4.2.
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>              Labels: derby_triage10_10
>             Fix For: 10.8.3.3, 10.9.2.2, 10.10.1.4, 11.0.0.0
>
>         Attachments: DERBY-5630.diff2, DERBY-5630.diff_try1
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message