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-5288) running multiple suites.All concurrently should be possible
Date Mon, 20 Jun 2011 19:56:47 GMT

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

Myrna van Lunteren updated DERBY-5288:

    Attachment: DERBY-5288_1.diff

Attaching a patch which removes the setting of the thread to MIN_PRIORITY and adds the join
on the streamReader thread with a time-out (otherwise there's a chance of hanging tests).

If there are no comments on this I intend to commit this and backport it to 10.8, 10.7, and
10.6, as those are the branches I think support running the junit tests concurrently.

With this change backported I did run a more successful concurrent run, although there were
still failures, but I think it's a good first step.

> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>                 Key: DERBY-5288
>                 URL: https://issues.apache.org/jira/browse/DERBY-5288
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:,,,
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-5288_1.diff
> When attempting to run multiple suites.All runs at the same time, using a different location
& jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message