Øystein Grøvlen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-230?page=all ]
Øystein Grøvlen updated DERBY-230:
----------------------------------
Attachment: derby-230b.diff
Attaching a new version of the patch where I have increased the
probability of the test reproducing the bug by increasing the
number of threads to 200. It now fails 16 out of 20 times on
a single-CPU machine. Increasing the number of threads further
seems to increase the execution time very much. Considering
that when running derbyall, the test is run three times in
different frameworks, the probability of the test suite detecting
the rebirth of this bug should be more than 98%. On a 2-CPU
machine the test failed 20 out of 20 times.
Hi Øystein,
Thanks for looking into this more. Given that, as you said, this is pretty
minor bug, and seeing has no one else has spoken up to object, I guess this
seems like an acceptable approach for now.
So I give it a +1, with one question: the latest patch that you submitted had
the following at the top:
-- <begin patch paste> --
Property changes on:
___________________________________________________________________
Name: svn:ignore
- classes
changenumber.properties
jars
javadoc
+ .ignore
*.diff
classes
jars
TAGS
testdir
-- <end patch paste> --
Your previous patches didn't have this in it, and I'm not sure what this is
doing. Do you know, or was this accidental? If it was accidental, then my "+1"
vote would be on the assumption that this was removed. If it's intentional,
then can you tell me briefly what this is doing?
Thanks for your patience,
Army
