On 10/29/2013 11:00 PM, Nathan Scott wrote:
Just running rest of QA now, 243 seems
to have failed, unrelated to above (first pmcd did not start so second
pmcd didn't get the expected bind(2) failure?) ... as has 283, similar
issue - pmcd not starting. Tests on-going, so others might crop up as
well yet - ~50% done.
Its just those two remaining now, I've fixed up the other few.
The following (see below) have been pushed to brolley/dev on pcpfans.
With these changes, both tests still fail with an extra message about
stopping pmlogger. I don't think that is related to the discovery stuff
and may even be the correct output.
243 - output mismatch (see 243.out.bad)
18a19
> Stopping pmlogger ...
Check local PMCD is still alive ...
PMDA probe: pminfo -h brolley-t510 -f sample.milliseconds
PMDA probe: pminfo -h brolley-t510 -f sampledso.milliseconds
PMDA probe: pminfo -h brolley-t510 -f simple.numfetch
283 - output mismatch (see 283.out.bad)
26a27
> Stopping pmlogger ...
Check local PMCD is still alive ...
PMDA probe: pminfo -h brolley-t510 -f sample.milliseconds
PMDA probe: pminfo -h brolley-t510 -f sampledso.milliseconds
PMDA probe: pminfo -h brolley-t510 -f simple.numfetch
Failures: 243 283
Failed 2 of 2 tests
--------------------------------------------------------------------------------
commit 60e87882d300c7cd6f1f78444f01adb81dafc9a0
Author: Dave Brolley <brolley@xxxxxxxxxx>
Date: Wed Oct 30 16:23:07 2013 -0400
Fix premature free of avahi service tag name.
Also filter Avahi service name collisions messages in qa test 283.
Completes the fix of qa test 243 and fixes qa test 283.
commit 7619ccfb8a06b033b51cd0160033eb44d1e57303
Author: Dave Brolley <brolley@xxxxxxxxxx>
Date: Wed Oct 30 16:22:20 2013 -0400
Revert previous change which opened the log before opening the
request ports.
Partially fixes qa test 243.
|