On 2/9/06, Mike Matrigali <[EMAIL PROTECTED]> wrote:
It would seem reasonable to mark this test to not run in nightly
under solaris 10 until you resolve the jvm issue or change the test.
Maybe someone can give some hints if this is possible under the
current test harness (I know it is pretty easy to mark not run
under a specific JVM, just not sure of OS).
 
The only way to handle os-specific details right now is to modify the test, or, for .sql files the *only* solution, to mask differing lines in the output using a <test>_sed.properties file, if the test doesn't fail too miserably.
 
There is no platform-specific skipping, or diffing.
 
Myrna

Reply via email to