pcp
[Top] [All Lists]

Re: [pcp] QA status - warning

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] QA status - warning
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 9 May 2013 19:10:29 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5189E7B2.30501@xxxxxxxxxxxxxxxx>
References: <51823EB3.1030003@xxxxxxxxxxxxxxxx> <851894341.11621320.1367881806756.JavaMail.root@xxxxxxxxxx> <2055430036.11651048.1367887214801.JavaMail.root@xxxxxxxxxx> <51889F39.8060206@xxxxxxxxxxxxxxxx> <86805787.12576575.1367970791260.JavaMail.root@xxxxxxxxxx> <51899D55.20202@xxxxxxxxxxxxxxxx> <1964501527.12596632.1367975338274.JavaMail.root@xxxxxxxxxx> <5189E7B2.30501@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: f/Fdl/D9YiaWGXJY0jJWqWqqbshGNQ==
Thread-topic: QA status - warning
Hi Ken,

----- Original Message -----
> [off list]

[back on list now, thanks for all those files]

> My system is like this ... (authentication=false and/or
> secure_sockets=false) may be clues to some of the failures.
> 
> $ pmconfig -L
> pmapi_version=2
> multi_threaded=true
> fault_injection=false
> secure_sockets=false
> ipv6=true
> authentication=false
> 
> Attached are all the .bad files and check.log.
> 

OK, here's my notes from looking through these failures.  I've
came back later and put a note with each as to who I think is/
might want to look further.

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]

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?]

116 - your laptop was switched off! :)  hah, my laptop is also my
      hyphen hostname host, and I get this too sometimes.
      [kenj]

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]

367 - hmm, test has linked the wrong .out file ... should be using
      the exercising the auth PDU on PCP_380, which the test did,
      but compared to pre-3.8.0 .out file (367.out.1) - could be a
      bad localconfig here?  passes for me.
      [setup issue - kenj?]

371 - this test is notrun for me (missing perl support module), hence
      I missed this.  the test is creating archives with log import,
      but uses invalid metric names.  according to pmns(4), components
       "must begin with an alphabetic character, and  be followed by
        zero or more characters drawn from the alphabetics,
        the digits and the underscore ââ_ââ) character."
      so, good.pmid.1 is not valid.  I'll update the test to use names
      like good.pmid.one and it will pass once more.
      [nathans]

374 - the .bad file you sent matches the expected output - this looks
      like it might be another case of localconfig not being correct?
375 - ditto
513 - and again (exercised the new auth PDU, but compared to older
      version of expected output)
      [setup issue - kenj?]

532 - pmlogger_daily - somehow a temp file not created (/tmp/pid.out.1)
      and several cascading errors resulted?  passes for me though.
      [???]

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?]


cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>