On 03/12/2012 09:46 AM, Gordon Sim wrote:
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?
Fyi: I've still not managed to trigger a crash unfortunately. The
failure seems more frequent under CI though, with 9 failures in the 17
builds since the first occurrence of this error.
The last commit for "QPID-3883: Using application headers in messages
causes a very large slowdown" is the change that coincides with the
first failure. Though that commit is unlikely to be the cause (it just
exports some symbols correctly for windows), the preceding changes for
the same JIRA could be related[1].
They seem the only likely candidates on the broker side. However its
always possible that a change on the java client side has uncovered an
existing issue.
[1] E.g. the following two commits which passed once before the first
failure:
http://svn.apache.org/viewvc/?view=rev&rev=1297292
http://svn.apache.org/viewvc/?view=rev&rev=1297290
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
