incubator-connectors-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CONNECTORS-172) Intermittent test failures
Date Fri, 01 Apr 2011 07:28:06 GMT

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

Karl Wright resolved CONNECTORS-172.
------------------------------------

       Resolution: Fixed
    Fix Version/s: ManifoldCF next
                   ManifoldCF 0.2
         Assignee: Karl Wright

r1087607
r1087610


> Intermittent test failures
> --------------------------
>
>                 Key: CONNECTORS-172
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-172
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Blocker
>             Fix For: ManifoldCF 0.2, ManifoldCF next
>
>
> The Derby filesystem end-to-end tests sometimes randomly fail with a "Database error:
No existing connection" error during a job status wait.  Not sure what's happening here, but
they succeed much of the time.  There's not much of a hint beyond the stack trace.  The message
seems to be coming from Derby, and may be the result of a too-short wait time limit, a race
condition in the test itself, or something else entirely.

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

Mime
View raw message