pcp
[Top] [All Lists]

New pdubuf-related QA failures

To: Dave Brolley <brolley@xxxxxxxxxx>, "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: New pdubuf-related QA failures
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 11 Mar 2015 21:38:02 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <2095979632.4368418.1426123690537.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: hJZQpWLq/9MoZziSS2XFQrKo+MB5hQ==
Thread-topic: New pdubuf-related QA failures
Hi guys,

828 and 833 are new failures from overnight commits - they look
likely to be just .out file issues, but I see 828 at least has
already been looked at (but still fails).  833 might be a lack
of valgrind installed on your test machine? - looks like its got
incorrect .out from not being run anyway; .bad files attached.

Also, ISTR at one point Ken asking for additional performance
data before this change was made, but don't remember seeing any
go past - was/is everyone content with this change?  Thanks.

cheers.

--
Nathan

Attachment: 833.out.bad
Description: Binary data

Attachment: 828.out.bad
Description: Binary data

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