You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/07/06 19:05:22 UTC
[jira] Updated: (DERBY-2862) ParameterMetaDataJdbc30 fails for
weme6.1, which prevents rest of suites.All from completing.
[ https://issues.apache.org/jira/browse/DERBY-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2862:
--------------------------------------
Issue Type: Test (was: Bug)
> ParameterMetaDataJdbc30 fails for weme6.1, which prevents rest of suites.All from completing.
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-2862
> URL: https://issues.apache.org/jira/browse/DERBY-2862
> Project: Derby
> Issue Type: Test
> Components: Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: A B
> Assignee: Ramin Moazeni
> Fix For: 10.3.1.1, 10.4.0.0
>
> Attachments: DERBY-2862.diff, DERBY-2862.stat
>
>
> With the addtion of the ParameterMetaDataJdbc30 JUnit test (DERBY-2658), suites.All has been failing with weme6.1. It turns out the that new ParameterMetaDataJdbc30Test fails with the following error:
> Failed to invoke suite():java.lang.NoClassDefFoundError: java.sql.ParameterMetaData
> which prevents suites.All from continuing and thus no results can be gathered.
> It might be good to disable the test for weme6.1 at least in the short term so that rest of suites.All can run cleanly again. Not sure if that's a complete solution or just a temporary one until the test can be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (DERBY-2862) ParameterMetaDataJdbc30 fails for
weme6.1, which prevents rest of suites.All from completing.
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
"Myrna van Lunteren (JIRA)" <ji...@apache.org> writes:
> [ https://issues.apache.org/jira/browse/DERBY-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Myrna van Lunteren updated DERBY-2862:
> --------------------------------------
>
> Issue Type: Test (was: Bug)
Since this is a bug in a test, I think it would be more correct to keep
the issue type "Bug" and instead add "Test" as a component.
According to
http://issues.apache.org/jira/secure/ShowConstantsHelp.jspa#IssueTypes,
issue type "Test" should be used for "A new unit, integration or system
test", which does not sound correct for this issue.
--
Knut Anders