On 07/16/2013 07:56 PM, Nathan Scott wrote:
So ... yes, git bisect did not lie, it is indeed the fault of the
change to enable pmie and pmlogger! But, not in a bad way, they are
actually running and doing what they are supposed to be doing - all
good. We need to handle this in the test - it needs to be
deterministic - even a remote possibility of these requests arrive
during the test needs to be removed. For now, we can simply add pmie
to the test 067 list of tools to signal before running (done). Longer
term, perhaps this test could be directed to make use of an alternate
PMCD_PORT which would be a better solution. cheers. -- Nathan
Interesting result. I changed the test to include 'export
PMCD_PORT=2223' and I still get the failures. The only thing that I can
think of is that the requests are coming in on the pmcd's own unix
domain socket. I haven't changed any clients to connect on that socket
by default (yet). Are you aware of any?
In any case, killing pmie may have to be the permanent solution.
-----------------------------------------------------------
067 - output mismatch (see 067.out.bad)
29,30c29,33
< ok FD 44321 inet INADDR_ANY
< ok FD 44321 ipv6 INADDR_ANY
---
> ok FD 2223 inet INADDR_ANY
> ok FD 2223 ipv6 INADDR_ANY
> [DATE] pmcd(PID) Error: pmdaFetch: Fetch callback error from metric
PMID 60.5.9[3]: Permission denied
> [DATE] pmcd(PID) Error: pmdaFetch: Fetch callback error from metric
PMID 60.5.7[3]: Permission denied
> [DATE] pmcd(PID) Error: pmdaFetch: Fetch callback error from metric
PMID 60.5.1[3]: Permission denied
|