----- Original Message -----
> On 12/02/15 15:39, Nathan Scott wrote:
> > Changes committed to git://git.pcp.io/pcp.git dev
> >
> > ...
>
> FWIW I have run the new/changed/previously failing qa tests on vm08 (x86_64
> CentOS Linux7.0.1406)
>
> 666 - extra lines
> + ==23969== could not unlink
> /tmp/vgdb-pipe-from-vgdb-to-23969-by-root-on-vm08.localdomain
> + ==23969== could not unlink
> /tmp/vgdb-pipe-to-vgdb-from-23969-by-root-on-vm08.localdomain
> + ==23969== could not unlink
> /tmp/vgdb-pipe-shared-mem-vgdb-23969-by-root-on-vm08.localdomain
>
See last mail to Dave & Frank - guess its a newer-valgrind-version
related issue.
> 720 - valgrind detected errors
> Command: pminfo -h
> pcp://localhost?user=NOsuchUSER&pass=DEFINITELYnotApassword
> + 39 bytes in 1 blocks are definitely lost in loss record 14 of 38
> + at 0x4C2A1D4: calloc (in
> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> + by 0x4E86ADB: __pmAuthSecretCB (secureconnect.c:750)
> + by 0x5C2459A: _plug_get_password (in /usr/lib64/libsasl2.so.3.0.0)
> + by 0x90BE45F: ??? (in /usr/lib64/sasl2/libdigestmd5.so.3.0.0)
> + by 0x90C29CA: ??? (in /usr/lib64/sasl2/libdigestmd5.so.3.0.0)
> + by 0x5C187F1: sasl_client_step (in /usr/lib64/libsasl2.so.3.0.0)
> + by 0x4E87825: __pmAuthClientNegotiation (secureconnect.c:1131)
> + by 0x4E8832C: __pmSecureClientHandshake (secureconnect.c:1213)
> + by 0x4E44126: __pmConnectHandshake (connect.c:175)
> + by 0x4E44746: __pmConnectPMCD (connect.c:413)
> + by 0x4E468EC: pmNewContext (context.c:525)
> + by 0x401860: main (pminfo.c:644)
Not seeing that here; its a new test - looks like possibly a genuine
failure though & a bug still remaining in libpcp/sasl code? commit
2ae6cd0a4ce may have exposed this reporting? Not sure, needs to be
investigated some more I think.
> 977 - kills pmcd, same as this morning's reported failure with pminfo -v
> --container=test
This ones near the top of my short-term list, thanks.
cheers.
--
Nathan
|