pcp
[Top] [All Lists]

pcp updates: python fix

To: PCP <pcp@xxxxxxxxxxx>
Subject: pcp updates: python fix
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 12 Oct 2015 02:55:19 -0400 (EDT)
Delivered-to: pcp@xxxxxxxxxxx
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: gFrdIs7F1M8H+FXoQM/sFeCrF1Pwpw==
Thread-topic: pcp updates: python fix
Changes committed to git://git.pcp.io/pcp.git master

Nathan Scott (2):
      qa: report output as float in python fsstats script for precision
      python api: ensure an interruptible sleep is used in python API


 qa/src/fsstats.python   |    2 +-
 src/python/pcp/pmapi.py |   10 ++++------
 2 files changed, 5 insertions(+), 7 deletions(-)


commit 40141eeec6162f17b17e9a0010ce438e7e365250
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date:   Mon Oct 12 11:52:50 2015 +1100

    python api: ensure an interruptible sleep is used in python API
    
    Turns out there's a poor interaction between signal handlers in the
    python interpreter and a libpcp nanosleep call that was underlying
    the timeval class sleep, which ended up not allowing the interrupt
    to be correctly caught and passed out of libpcp.
    
    Resolved by using pythons own sleep interfaces which are sub-second
    precision also.
    
    Fixes Red Hat BZ #1238550.

commit 3f0ebbe9cfcc2a0ca2f0f10b36eef1fd849db5a8
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date:   Mon Oct 12 11:47:48 2015 +1100

    qa: report output as float in python fsstats script for precision
    
    The underlying pmcc module is using double precision for numeric
    metric values, but the script was reporting everything as integer.
    May or may not help with a 32/64 bit precision issue kenj has seen
    but its better to make this change anyway.

<Prev in Thread] Current Thread [Next in Thread>
  • pcp updates: python fix, Nathan Scott <=