[cgl_discussion] RE: Validation Test Suite for Scalability pa tches

Fleischer, Julie N julie.n.fleischer at intel.com
Tue Sep 10 13:22:10 PDT 2002


One question:  Are there any tests we would want to pull out and make into
an ABAT for scalability?  If so, then those could go into the
scalabilityenhancements directory.

ABAT is for really simple tests.  Like maybe checking the size of some file
system or something?  It seems like we might be able to make something small
for ABAT here....

- Julie

------------------------------------------------------------------------
Julie Fleischer
Intel Corporation
julie.n.fleischer at intel.com

This email message solely contains my own personal views, and not
necessarily those of my employer.


-----Original Message-----
From: Lynch, Rusty [mailto:rusty.lynch at intel.com]
Sent: Tuesday, September 10, 2002 1:07 PM
To: 'Stephanie Glass'; Lynch, Rusty
Cc: 'cgl_discussion at osdl.org'; Peddibhotla, Rammohan; Lisa Perry;
mika at osdl.org
Subject: [cgl_discussion] RE: Validation Test Suite for Scalability
patches


Let's use the existing LTP suite, but still add a test suite to the
directory structure for "scalabilityenhancements" or whatever the
requirement name is.  The new suite would contain a README that explained
that the implementation for the test are really handled under the LTP suite,
an entry in the spec file that made a runtime dependency on the "ltp" suite,
and a wrap.sh that called into the other suite to execute whatever test are
appropriate and produce a results.txt structured in the standard format.

Does that make sense?  If you want I can easily put together a new
"scalabilityenhancements" suite that does all of the above except for the
correct logic inside wrap.sh.

The advantage of maintaining a "scalabilityenhancements" suite is that we
can still use the directory structure to enforce tractability like we
designed in the framework specification.  The suite would still follow all
the rules of a validation suite since it would be located in the correct
directory, still be started in the standard way, and still report results in
the standard way.  The fact that the suite depends on some other code is an
implementation detail.

	-rusty 



-----Original Message-----
From: Stephanie Glass [mailto:sglass at us.ibm.com]
Sent: Tuesday, September 10, 2002 12:51 PM
To: Lynch, Rusty
Cc: 'cgl_discussion at osdl.org'; rammohan.peddibhotla at intel.com; Lisa
Perry; mika at osdl.org
Subject: Validation Test Suite for Scalability patches



Rusty,
I'm not suer of the procedure for doing this, so I thought I would ask
before I just did it.

I am listed as the maintainer for the Scalability patches.  Those patches
are covered for FVT with the LTP test suite.  I don't really want to create
another version of the LTP and call it Scalability patches.  I also, don't
really want to rename LTP to Scalability patches since the community
already knows those tests as the LTP.  When I write the test plan for
Scalability patches, can I just reference the LTP and give the location
where the tests are?  What do you want to see happen for this feature?

Thanks.

Stephanie

Linux Technology Center
 IBM, 11400 Burnet Road, Austin, TX  78758
 Phone: (512) 838-9284   T/L: 678-9284  Fax: (512) 838-3882
 E-Mail: sglass at us.ibm.com

_______________________________________________
cgl_discussion mailing list
cgl_discussion at lists.osdl.org
http://lists.osdl.org/mailman/listinfo/cgl_discussion



More information about the cgl_discussion mailing list