pcp
[Top] [All Lists]

qa/720 - very unreliable

To: PCP <pcp@xxxxxxxxxxx>
Subject: qa/720 - very unreliable
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Mon, 16 Feb 2015 16:32:16 +1100
Delivered-to: pcp@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
I have 15 different failures for qa/720 across 16 systems.

Broadly they are

1. assortment of error message types, text, format, etc from pminfo, for example
101c101
< pminfo: Cannot connect to PMCD on host "pcp://localhost?user=NOsuchUSER&pass=DEFINITELYnotApassword": Authentication - authentication failure
---
> Error: Authentication - user not found

Is there any technically plausible reason that these should be treated as synonymous and magically filtered into a passing test?

2. valgrind failures in a blinding assortment of variations around _plug_get_password ... I'm currently trying a minimalist valgrind suppression of the form

{
   cyrus-sasl callback leak, RHBZ1191183, common case variant
   Memcheck:Leak
   fun:calloc
   ...
   fun:_plug_get_password
   ...
   fun:sasl_client_step
   ...
}

Does this look OK?

How are others going with this test?

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