Hi Ken,
I'm seeing the following failure on several hosts:
$ ./check -q -l 628
628 27s ... - output mismatch (see 628.out.bad)
4c4
< value 3
---
> No value(s) available!
16c16
< value 4
---
> No value(s) available!
I've git bisected it to the recent e_ext_t changes, I think (its
behaviour seems to have some dependence on uninitialised memory,
so its not 100% certainly that commit). I've never seen it fail
without that commit in play though, and since I've never seen it
before either, it has to be something very recent and something
that affects pmcd/pmda_simple.so - that one's the only candidate
change I can see.
This test is exercising 2 DSO PMDAs and basic value fetches. They
both use PMDA_INTERFACE_2, which looks like a factor - the change
to fetch callback return code being zero/non-zero was after v2. A
'No values' being returned from pminfo may indicate PMDA version
confusion at the pmcd (libpcp_pmda) end of the connection?
Beyond that, its proving really difficult to diagnose. Could I
get you to take a closer look when you get some time? I think it
is best to revert this change for this release, and reinstate it
in dev for 3.10.2 while investigations continue. Let me know if
its something that is immediately obvious, or if not reproducible
I'll continue the hunt next week.
thanks!
--
Nathan
|