pcp
[Top] [All Lists]

Re: New bug in case 633 with pcp-2.3.0-8

To: "Zhang, Sonic" <sonic.zhang@xxxxxxxxx>
Subject: Re: New bug in case 633 with pcp-2.3.0-8
From: kenmcd@xxxxxxxxxxxxxxxxx
Date: Mon, 13 Jan 2003 10:24:33 +1100 (EST)
Cc: "PCP (E-mail)" <pcp@xxxxxxxxxxx>
In-reply-to: <957BD1C2BF3CD411B6C500A0C944CA2602BCEDAA@pdsmsx32.pd.intel.com>
Reply-to: kenmcd@xxxxxxxxxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Wed, 8 Jan 2003, Zhang, Sonic wrote:

> Hi,
> 
>       See the attachment.
> 
>       Sonic Zhang
> 
> ----------------------------------------
> diff 633.out 633.out.bad
> 2,3c2,3
> < 4 pmGetPDU: DESC
> < 1 pmGetPDU: ERROR
> ---
> > 3 pmGetPDU: DESC
> > 3 pmGetPDU: ERROR

There have been some problems with this test over the years, and I've
never been able to pin the root cause down.  Do you still have the
633.full output from this failure?  If so, could you please send me
that file.

And in general (not just for Sonic) the tests that are most likely to
fail are the ones that also produce an NNN.full output file ... this
is never used in determining pass/fail for a test, but is invaluable to
trying to diagnose why a test failed ... so when seeking assistance for
QA test failures, please make sure to include not only the NNN.out.bad
file, but also the NNN.full file if one was created.



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