pcp
[Top] [All Lists]

pcp updates: qa

To: pcp developers <pcp@xxxxxxxxxxx>
Subject: pcp updates: qa
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 3 Aug 2016 20:54:28 -0400 (EDT)
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1304646301.14245503.1470271636026.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: LsudG8OjfO8sl+5rhVGadJpM5kbIfA==
Thread-topic: pcp updates: qa
Changes committed to git://git.pcp.io/pcp.git master

Ken McDonell (1):
      qa/200: filter out __pmCloseChannelbyContext lines

Nathan Scott (1):
      qa: sasldb user account bug detection in test 823


 qa/200     |    1 +
 qa/200.out |    5 -----
 qa/823     |   22 +++++++++++++++++-----
 qa/832     |   18 +++++++++++++-----
 4 files changed, 31 insertions(+), 15 deletions(-)


commit 9352ebbebd2cced91c3595f1e61ef542e83345b3
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date:   Thu Aug 4 10:45:32 2016 +1000

    qa: sasldb user account bug detection in test 823
    
    After much protocol analysis on affected machines, its
    clear older versions of SASL are just not handling the
    sasldb case correctly.  Detect this, and handle it more
    gracefully.  Extend all SASL tests so they work on some
    platforms where pluginviewer command is installed with
    a different name (sasl-prefixed) - previously the tests
    would have notrun there, when they could have.

commit c96ffd8d79478a11702fccc7600cd7f61fb05d99
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Thu Aug 4 07:00:37 2016 +1000

    qa/200: filter out __pmCloseChannelbyContext lines
    
    The termination of the context in this test is not deterministic,
    so in some cases we see a normal end-of-file (no diagnostic) and
    in other cases a partial PDU is delivered or end-of-file is
    encountered unexpectedly ... simplest to filter out the recently
    added __pmCloseChannelbyContext diagnostic.

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