[Swift-devel] Testing for new releases

[David Kelly]

In the configuration matrix, an entry exists for "CI machines." Are
these the thwomp, stomp, crush, sneezy, grumpy, and doc machines
@mcs.anl.gov?

Thanks,
David

On Tue, Jan 4, 2011 at 9:00 PM, Sarah Kenny <skenny at uchicago.edu> wrote:
> trying to make a matrix out of the matrix...first pass feel free to correct
> :)
>
> http://www.ci.uchicago.edu/wiki/bin/view/SWFT/ReleasePlans#site_specific_tests
>
> On Tue, Jan 4, 2011 at 2:29 PM, Justin M Wozniak <wozniak at mcs.anl.gov>
> wrote:
>>
>> On Tue, 4 Jan 2011, David Kelly wrote:
>>
>>> During today's conference call, a matrix of configurations was
>>> mentioned which contained a preliminary list of what needed to be
>>> supported. Where is this list located?
>>
>> http://www.ci.uchicago.edu/wiki/bin/view/SWFT/ReleasePlans
>>
>>> So the overall plan, as I understand it:
>>>
>>> 1) Finish writing tests for configurations listed in the matrix
>>> 2) Verify the tests work with the 0.92 release and report any issues
>>> 3) Automate the tests with meta.sh
>>
>> Full automation of meta.sh is not required for 0.92.  Let's start by using
>> it to create an outline of what it could do via ssh.  Once we see what that
>> looks like we can turn it into a real tool.
>>
>>> 4) Make these verified configurations available to users via a well
>>> documented swift road map
>>>
>>> In terms of directory structure for site tests.. if I want to create a
>>> specific test for PADS, for example, should I create it within
>>> tests/providers/local-pbs/PADS/?
>>
>> This looks good.
>>
>> --
>> Justin M Wozniak
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>