db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: [jira] [Updated] (DERBY-2076) Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
Date Mon, 18 Jun 2012 14:49:23 GMT
On Mon, Jun 18, 2012 at 6:14 AM, Kristian Waagan (JIRA) <jira@apache.org> wrote:
>
>     [ https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>
> Kristian Waagan updated DERBY-2076:
> -----------------------------------
>
>    Attachment: derby-2076-0b-modernized_compat_test_preview.diff
>
> Attaching an updated version of the modernized compatibility test. Here's what running
the MATS looks like (with trace and debug enabled):
>
[...skip...]
>
> This is still not ready for commit.
> Given this will be enabled by default in suites.All, do people prefer that the test fails
if there are no old releases available, or rather that an ALARM statement is printed?
>

I would prefer an ALARM.

Myrma

Mime
View raw message