pcp updates: changes for a QA world that avoids systemd

Changes committed to git://git.pcp.io/kenj/pcp master

Ken McDonell (3):
      qa: need a bit more care with set/restore $PCPQA_SYSTEMD
      qa/964: refactor
      qa: assorted *_auto_restart changes to stop systemd interference

 qa/172     |   15 +++++++-
 qa/183     |   12 +++++-
 qa/187     |   10 ++++-
 qa/192     |    3 +
 qa/657     |   15 +++++++-
 qa/666     |    2 +
 qa/805     |   15 +++++++-
 qa/831     |   13 ++++++
 qa/831.out |    3 +
 qa/964     |  114 ++++++++++++++++++++++++++++++++++++++++++++-----------------
 qa/964.out |   15 +++++---
 11 files changed, 175 insertions(+), 42 deletions(-)

Details ...

commit 5fb597c4dee22e6c629a2e5d9c3381b473e52057
Author: Ken McDonell <[email protected]>
Date:   Fri Feb 10 07:27:03 2017 +1100

    qa: assorted *_auto_restart changes to stop systemd interference

    With the use of PCPQA_SYSTEMD=no on my QA Farm, I have exposed
    some more tests that need prophylactic protection from systemd
    autorestarting.

    These tests were passing on systems without systemd, but there were
    assorted failures when systemd was active, mostly as a result of
    the test stopping a PCP daemon and then the test and systemd getting
    in an arm wrestle over who's restarting the daemon ... the QA tests
    invariably lose these battles.

commit b328aa8c74b47807246e7fb15d7751ff0ccb370f
Author: Ken McDonell <[email protected]>
Date:   Fri Feb 10 07:23:05 2017 +1100

    qa/964: refactor

    This test has fallen on hard times in the wake of the pmlogger changes
    to allow it to survive pmcd restarts, and somewhat dodgey logic that
    was associated with counting pmlogger instances.

    Reworked to run two PMDA installs ... one does not require a pmcd
    restart (xfs) and one does require a pmcd restart (dm).  Check the
    same primary pmlogger continues to run through both PMDA installs.

    Also needed some extra care in the notrun guards and the trap
    handling of the PMDA cleanup.

commit 156fb6ec2751bc48002e3d3fb5f9476e33f778d0
Author: Ken McDonell <[email protected]>
Date:   Fri Feb 10 07:17:47 2017 +1100

    qa: need a bit more care with set/restore $PCPQA_SYSTEMD

    Now I'm using $PCPQA_SYSTEMD=no to stop systemd messing with QA,
    I need to be a little less cavalier about setting and unsetting
    PCPQA_SYSTEMD in those tests that specifically must avoid
    systemd on all platforms.

    These changes restore PCPQA_SYSTEMD to its initial state before
    the final _service restart.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#15101): https://groups.io/g/pcp/message/15101
View All Messages In Topic (1): https://groups.io/g/pcp/topic/4351773
Mute This Topic: https://groups.io/mt/4351773?uid=174580
New Topic: https://groups.io/g/pcp/post
-=-=-
pcp mailing list
[email protected]
https://groups.io/g/pcp/messages
-=-=-
Change Your Subscription: https://groups.io/g/pcp/editsub?uid=174580
Group Home: https://groups.io/g/pcp
Contact Group Owner: [email protected]
Terms of Service: https://groups.io/static/tos
Unsubscribe: https://groups.io/g/pcp/leave/354243/563757577/xyzzy
-=-=-=-=-=-=-=-=-=-=-=-