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] [Updated] (DERBY-5630) intermittent test failure in store/lockTableVTI.sql
Date Wed, 05 Feb 2014 01:56:08 GMT

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

Myrna van Lunteren updated DERBY-5630:
--------------------------------------

    Attachment: DERBY-5630.diff2

The problem I was seeing in the failed situation was that the assert was bailing out of the
test fixture and so the instructions to let the secondary thread continue were not reached.


This patch adjusts that situation and:
- removes the old lockTableVti.sql from the StoreScriptsTest
- adds the new LockTableVtiTest to store._Suite
- deletes store/lockTableVti.sql and mastter/lockTableVti.out

Another modification is that there are no asserts in the internal AsyncThread class; asserts
there did not cause the test to fail, and it's not really important to the test.

I will commit this patch shortly.

> 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
>              Labels: derby_triage10_10
>         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