On 11/02/16 16:12, Nathan Scott wrote:
----- Original Message -----
Details for the most commonly failing tests are available from
ftp://oss.sgi.com/projects/pcp/download/qa-status/
(this is great, thanks Ken).
I plan to post weekly all the while it is useful.
...
QA Test Fail Failure Signatures (number of different failure patterns)
878 10 6 2 2
These appear to be race conditions - I've pushed through a handful of
changes to make things more reliable on slower hosts, let's see how
that goes.
I'm still seeing failures ... I did some triage of this at the PDU level
and the behaviour appears to be non-deterministic, even within a group
of passing and a group of failing tests, ... at that point I decided
there were other things to look at ...
802 5 5
This one's odd - appears to be new this week, but there's nothing I can
think of since the previous run that would have induced this (dbpmda is
seeing a timeout on PMDA start?) ... something in libpcp? Surely not.
One of the problems with a weekly report is that late breaking fixes are
not reflected in the results ... in this case the commit below has
knocked 802 out of the hit list ...
commit 5f56df40ad46054a572b6aed0b75103a3fae5f3f
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue Feb 9 13:29:26 2016 +1100
qa/802: fix timing-related failure
Need extra delay to overcome tardy valgrind startup on some VMs.
|