pcp
[Top] [All Lists]

Re: [pcp] Recent QA failures

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Recent QA failures
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 27 Apr 2015 20:12:11 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <026e01d07fa2$874e9cd0$95ebd670$@internode.on.net>
References: <026e01d07fa2$874e9cd0$95ebd670$@internode.on.net>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AdB/ogYiRwN31L4ERXGHXcMcTPGWrOg8ExFL
Thread-topic: Recent QA failures

----- Original Message -----
> I'm seeing failures on these tests: 458 800 982 995
> 
> These appear to be new and recent regressions.
> 
> The spread is pretty broad, so not likely to be a single cause ...
> 
> kenj@bozo-vm:~/src/pcp/qa$ egrep '^(458|800|982|995)' group
> 458 pmda.logger pmda.install event local
> 800 pmda.proc local
> 982 pmda.proc pmda.hotproc local
> 995 python local
> 
> .bad files attached

995 looks like either the "python-pcp" or "python3-pcp" package has not
been updated?  Its passing here for both python2 & 3 and I'd expect the
failure you're seeing there if the pmapi.py was out-of-date.

458 looks like either a pmdalogger issue or a race condition - nothing
I can think of that has changed there recently, so odd that its started
failing.

cheers.

--
Nathan

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