Hi Ken,
----- Original Message -----
> I need someone to help resolve the problem below that I reported several
> days ago and leaves rpm packaging broken on at least Fedora 18.
Did 3.7.2 work on this host (vm03)? I don't think we've got anything
new/changed in the perl build since 3.7.2, so seems odd. If it passed
in 3.7.2, then there might be something strange in the qa host setup -
the auto-builders here had no problem with f18 (although that's not
using the Makepkgs script).
> == Packaging pcp, log is in /home/kenj/src/pcp-dev/Logs/pcp
> Packaging failed, see log in /home/kenj/src/pcp-dev/Logs/pcp
(anything interesting in the tail of that log file?)
> Appending installation info to
> /tmp/pcp-build-32533/home/kenj/perl5/lib/perl5/x86_64-linux-thread-multi/perllocal.pod
> Arrgh ... no files to include in package via ../../../perl-pcp-pmda.list
>
> >
> > 024 - mmv pmda coming & going ... think this is as a result of
> > the earlier attempts to get consistent pmda setups for all
> > tests? can we force mmv to always be there? (and dso)
> > [at this stage, I've been assuming kenj'll tackle this]
>
> Fixed with a recent commit of mine ... cause is subtle and only
> peripherally related to consistent pmda setups.
>
Good catch, didn't think of that - thanks.
> > 051 - looks like fallout from the wildcard changes? specific to
> > either your network or non-secure sockets though, as its
> > passing for me? I'll do a non-secure-socket QA run today
> > and send further mail as to which it is.
> > [one for kenj/brolley to nut out?]
>
> Not sure on this one, I have a mixture of passes and fails ... no clear
> picture yet.
Ah, I still need to do that non-secure test run - will do today.
> > ...
> > 359 - pmdasystemd failure - all metrics getting illegal pmid
> > (this is notrun for me, I have no QA hosts sufficiently modern
> > as yet - on the todo list, but wont happen overnight)
> > [fche? - see test 652 as well, looks related]
>
> Is being run and passing on other hosts, so not sure about this one.
I had another look into this one, and I'd punt this is a test failure.
this test is susceptible to residual metric names in the namespace, and
somehow you had pmdasystemd names in the PMNS at the start of the test,
but no pmcd.conf entry for that PMDA. I think.
> > 367 - hmm, test has linked the wrong .out file ... should be using
> > ...
> but that's not the problem. On several hosts I have
> authentication=false from pmconfig -L, but the .bad file seems to match
> 367.out.2
>
> Should the guard be checking PCP_VER or are there 3 possible output
Yes, thats correct - the guards were wrong, and it should indeed be a
PCP_VER check - fixed now, thanks.
>
> > 374 - the .bad file you sent matches the expected output - this looks
> > like it might be another case of localconfig not being correct?
>
> Not a config problem on another host with the same symptom. Seems like
> this commit 0df386edf0d94119d46ee849ccc91a82d6911e33 changed the pmns
> for the pmcd PMDA, but some consequential change is needed for the QA test.
>
Hmm, right you are, ah I think I have missed this one as some of my remote
hosts were up/down/missing/running older dev PCP versions at various times.
Will be fixed with my next set of commits.
> > 513 - and again (exercised the new auth PDU, but compared to older
> > version of expected output)
> > [setup issue - kenj?]
>
> Not a setup issue. Same as 367 (but no typo this time).
Yep, fixed now.
> > 532 - pmlogger_daily - somehow a temp file not created (/tmp/pid.out.1)
> > and several cascading errors resulted? passes for me though.
>
> Seems to be passing now.
> >
> > 652 - another systemd failure - oh, looks like the metrics changed (ISTR
> > suggesting this) and perhaps the test was not updated? Lets prod
> > Frank for his verdict, but this looks to me like a bad .out file.
> > [fche - possibly just a qa/remake needed by kenj?]
>
> Can't test due to rpm build issue above. Not obviously run elsewhere.
>
Should work now, Franks confirmed that a remake was in order.
cheers.
--
Nathan
|