You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2011/03/25 19:40:06 UTC
[jira] [Created] (CONNECTORS-172) Intermittent test failures
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
Priority: Minor
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
[jira] [Resolved] (CONNECTORS-172) Intermittent test failures
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CONNECTORS-172) Intermittent test failures
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014098#comment-13014098 ]
Karl Wright commented on CONNECTORS-172:
----------------------------------------
Seems to be a Derby problem. DERBY-5169 created.
> 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
> Priority: Minor
>
> 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
[jira] [Updated] (CONNECTORS-172) Intermittent test failures
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright updated CONNECTORS-172:
-----------------------------------
Priority: Blocker (was: Minor)
> 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
> Priority: Blocker
>
> 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