On 03/11/2012 06:10 PM, Robbie Gemmell wrote:
Hi all,
Just thought I'd post this here to make sure it gets seen, I know many
people filter the JIRA traffic.
I was taking a quick look at why there has been an notable increase in
failures of the test job Keith had set up to run against the C++
broker on the ASF Jenkins instances. It seems one test in particular
(which I added earlier last year to verify a defect fix for the Java
broker) has been sporadically failing over the last week or so.
Investigating the logs for the last failure suggest the C++ broker
segfaulted during the test run, which lead on to the eventual test
failure report.
I have raised the following JIRA and attached the latest test log to
it as they dont get kept long. I have marked it as criticial for now,
although as it appears to affect the 0.16 branch too I'd actually
probably consider it a blocker at this point (but since theres no
chance of me being able to fix it, I figured I would let those with a
clue about the C++ broker make that decision).
https://issues.apache.org/jira/browse/QPID-3893
C++ broker appears to segfault during MultipleTransactedBatchProducerTest
I wasn't able to trigger a failure locally; will look for a box with
more processing available as I suspect the level of concurrency may be a
factor. I don't suppose there were any cores on that box from the segfault?
I agree with your assessment as critical until we uncover what the issue
is, whether its a regression, what the scope of the fix might be etc etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
