Re: [eclipselink-dev] Exclude QueryTimeoutTest from Core SRG?

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Sabine,

  The requirement is actually that there are no failures in the Core SRG. 
Skipping a test with committer approval satisfies that requirement.  Unless 
there is a committer who disagrees, adding code to skip the test in MaxDB 
similar to the Symfoware code is ok.

  I am ok with that change.  I assume any committer who disagrees with that 
change will respond to this email today.

-Tom

Heider, Sabine wrote:
> Hi,
>  
> MaxDB’s JDBC driver doesn’t support the setQueryTimeout method as 
> documented in _bug 326503_ 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=326503>. Due to this 
> limitation, the following tests fail:
>  
> org.eclipse.persistence.testing.tests.queries.QueryTimeoutTest
> org.eclipse.persistence.testing.tests.queries.QueryTimeoutConnectionReleasedTest
>  
> QueryTimeoutTest is part of the Core SRG test suite, and according to 
> the rules for database platform promotion, a platform is required to 
> pass Core SRG without failures.
>  
> Both tests are skipped for the Symfoware platform where the same 
> limitation applies. I guess, however, that this was done before the 
> rules for database platform promotion have been set up in this form, 
> wasn’t it? How should we proceed here? Should the QueryTimeoutTest 
> rather be excluded from Core SRG?
>  
> Thanks for your advice and best regards,
> Sabine
>  
> *Sabine Heider
> **SAP AG
>
> *Pflichtangaben/Mandatory Disclosure Statements:
> _http://www.sap.com/company/legal/impressum.epx_
>  
>  
>  
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev