On Thu, 26 Dec 2002, Zhang, Sonic wrote:
> Hi,
>
> I am now running the PCP test suite. I find that some host names are
> hard-coded in the test scripts, such as "moomba.melbourne.sgi.com" in case
> 77.
OK, this is a problem in 077 ... I'll have to re-engineer the test to
be more generic.
I suspect there are only a few remaining cases like this.
> Because my test host has a different name, I have to revise each of
> those name string manually. I think it is better to make all host name an
> environment variable. What's your opinion?
No, any test that has some "sgi" hostname hardcoded into it needs to be
reworked to remove the dependency ... there is already a generic scheme
for chosing local hosts and filtering the output to make the results
generic ... the ones you're running into are some feral examples that
were probably developed very early on before the generic schemes had been
put in place and have been overlooked as they never failed when run inside
sgi.
> I setup 3 machine for test, 2 of them have only 1 CPU while another
> has 2. I install the test suite on all of them. There are a few failures, I
> will send some *.out.bad files for your reference soon.
OK, I'll work through 'em one at a time.
> Thanks.
>
> Sonic
>
> -----Original Message-----
> From: kenmcd@xxxxxxxxxxxxxxxxx [mailto:kenmcd@xxxxxxxxxxxxxxxxx]
> Sent: 2002?12?25? 6:32
> To: Zhang, Sonic
> Cc: PCP (E-mail)
> Subject: Re: Are there any documents about the test suite?
>
>
> On Mon, 23 Dec 2002, Zhang, Sonic wrote:
>
> > Hi,
> >
> > I am a user of PCP. I downloaded PCP test suite from the SGI FTP
> > site.
> > After I configure the test suite according to the README file and
> > execute it, I find that some test cases fail.
> > Are there any brief documents to describe what each case does? I
> > didn't find any information in the test suite tar ball.
>
> I'm afraid there is no additional information ... after the README, you'll
> have to look at the individual test scripts and the source applications.
>
> Failures typically fall into one of 3 categories ...
>
> 1. setup ... lots of tests fail in a similar fashion ... check the
> availability of remote QA hosts running PCP and the PMDA installations.
>
> 2. generalization errors ... things work for us, but not for you because
> of subtle differences in the environment, the platform, etc.
>
> 3. porting errors and functional failures.
>
> For 1. you're on your own. For 2., we are interested in working with
> you to generalize the tests so that they pass automatically in as many
> environments as possible. For 3. you're on your own again.
>
> If you send me a couple of the *.out.bad files I can help you decide
> which classes of failures you're seeing.
>
|