[dna-issues] [JBoss JIRA] Updated: (DNA-198) JackrabbitDerbyStressTest throws exceptions intermittently without failing
Randall Hauch (JIRA)
jira-events at lists.jboss.org
Tue Aug 12 12:06:40 EDT 2008
[ https://jira.jboss.org/jira/browse/DNA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Hauch updated DNA-198:
------------------------------
Description:
Attached file contains a sample of output. The output shows several errors are logged beginning with the 1000 node test, but I've seen that particular test work sometimes without the error being logged (when run along with the rest of the test class). If each test method is run separately, each test seems to pretty consistently run without logged errors.
Note that this problem does not result in a test failure.
was:Attached file contains a sample of output. The errors in this case begin with the 1000 node test, but I've seen that particular test work sometimes without the error (when run along with the rest of the test class). If each test method is run separately, each test seems to pretty consistently run without error.
Priority: Minor (was: Major)
There doesn't appear to be a specific Jackrabbit issue regarding this, although several issues have been reported under other activities (e.g., ) that describe getting this error. I don't know whether it's a Jackrabbit issue or a Derby issue. Since Maven does not consider this a failure (description was updated to make this clear), lowering the priority.
> JackrabbitDerbyStressTest throws exceptions intermittently without failing
> --------------------------------------------------------------------------
>
> Key: DNA-198
> URL: https://jira.jboss.org/jira/browse/DNA-198
> Project: DNA
> Issue Type: Bug
> Components: Testing
> Affects Versions: 0.1
> Reporter: Johnny Verhaeg
> Priority: Minor
> Fix For: 0.2
>
> Attachments: JackRabbitDerbyStressTestFailure.txt
>
>
> Attached file contains a sample of output. The output shows several errors are logged beginning with the 1000 node test, but I've seen that particular test work sometimes without the error being logged (when run along with the rest of the test class). If each test method is run separately, each test seems to pretty consistently run without logged errors.
> Note that this problem does not result in a test failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the dna-issues
mailing list