pcp
[Top] [All Lists]

pcp updates: qa & pmcd diagnostics

To: pcp@xxxxxxxxxxx
Subject: pcp updates: qa & pmcd diagnostics
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue, 5 Jan 2016 16:54:56 +1100
Delivered-to: pcp@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
Changes committed to git://git.pcp.io/kenj/pcp master

Ken McDonell (3):
      qa/381: fix logic error related to pmlogger control port
      src/pmcd and src/libpcp_pmcd: improved diagnostics
      qa/578: finally found cause of random failures

 qa/381                      |   55 ++++++++++++++++++++++++++++++--------------
 qa/381.out                  |   32 ++++++++++++-------------
 qa/578                      |   12 +++++++--
 qa/578.out.1                |    1 
 qa/578.out.2                |    1 
 src/libpcp_pmcd/src/trace.c |    6 ++--
 src/pmcd/src/pmcd.c         |   10 ++++++--
 7 files changed, 74 insertions(+), 43 deletions(-)

Details ...

commit 233daf198a96dfda4dfbf73044010cd7ed4c5470
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Tue Jan 5 16:48:52 2016 +1100

    qa/578: finally found cause of random failures
    
    Since we introduced unix: as a channel to the local pmcd, it is no
    longer safe to start pmcd with PMCD_PORT set to something non-standard
    and assume the qa test is the only one talking to this pmcd.
    
    Need to work harder to kill off all client connections to the test
    pmcd instance ... it is a BIG deal for this test as it is checking
    for pmcd fd leakage, and stray clients connection mess the test up.

commit ee2433dcef79ea8f46d81bc92e7e2c088fa0022b
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Tue Jan 5 16:46:25 2016 +1100

    src/pmcd and src/libpcp_pmcd: improved diagnostics
    
    1. redirect log asap to avoid early messages escaping on stderr
       (only known to be an issue if pmDebug != 0)
    2. improve connection tracing details when a client closes the
       connection to pmcd

commit 7e1631343c08cc5b14ef929149f858718e194f95
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Mon Jan 4 16:14:05 2016 +1100

    qa/381: fix logic error related to pmlogger control port
    
    The test assumed the remote primary logger would be on port 4330 ...
    this is not always the case, so rejig to get the real port for the
    primary pmlogger from the remote pmcd PMDA.

<Prev in Thread] Current Thread [Next in Thread>
  • pcp updates: qa & pmcd diagnostics, Ken McDonell <=