Hi all,
Short note about QA - I have just the two failures at the moment,
so things seem to be in pretty good shape. It would be wonderful
if other folk with time to spare at the moment can crank up their
testing efforts as we move toward the next release.
The two failures I have on dev branch are:
438 - bad file attached; appeared around the time of some of the
new logcheck work or possibly start of the month (midyear);
not clear if either of these events are related but its in
the logging code (pmLogSetTime). Had never seen a failure
here before, so worth deeper investigation. (have you come
across this one yet Ken? keen to hear your thoughts there)
831 - the new unix domain socket test, was working but seems to
have spontaneously combusted and is now reliably getting a
ENOENT error on client connection. (I'll look into this one
early next week, or Dave can grab it if he's quick)
For myself I'm planning work on further testing, bug fixing (esp.
in pmchart) and last minute auth/acl work (and its documentation),
in the lead up to next release. I'm thinking end of next week for
updates to both pcp and pcp-gui to pick up the latest and greatest
bits from everyone.
Please help with testing, and get any pending code in as early as
possible if its intended for these two releases - thanks!
cheers.
ps: there's a test somewhere that is leaving tmpfiles in the test
directory, and not cleaning up as it should:
-rw-------. 1 pcpqa pcpqa 0 Jul 18 22:26 wuxcSU
... I have no idea which one though - but it should be using $tmp.
--
Nathan
438.out.bad
Description: Binary data
|