New tests that break regression suite should be backed out of suite. A
reasonable exception is if the submitter is actively working on fixing
the problem, and let's the community know it.
If I had committed the change then I would feel it was my job to back it
out if the submitter doesn't look like they will be able to get to it.
Hopefully having a clean regression suite run is an itch that at least
all the committers are interested in.
Myrna van Lunteren (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-999?page=comments#action_12368560 ]
Myrna van Lunteren commented on DERBY-999:
------------------------------------------
Imho it should not have gotten into the suite. Instead of providing valid testing, it has provided extra work.
It is a regular irritant because the test keeps failing with this jvm, and from the response by the creator on the list it is clear that the creator has little intent (no itch. :-) ) to correct this for ibm142, instead expecting it to be automagically fixed when the functionality goes in for full.
test SURTest.junit fails with ibm142
------------------------------------
Key: DERBY-999
URL: http://issues.apache.org/jira/browse/DERBY-999
Project: Derby
Type: Bug
Components: Regression Test Failure
Versions: 10.2.0.0
Reporter: Myrna van Lunteren
Priority: Minor
Attachments: SURTest.diff, SURTest.out, SURTest.tmpmstr
The test SURTest.junit fails with ibm142.
I'm attaching the .diff, .out, and . tmpmstr files.
