[Gluster-devel] Is there a Regression Test cycle exist?

[ender]

Thankfull large testing environments are easy these days with virtual machines.
Zhou i wanted to improve on your Failover test idea with the following:
d)         Failover test. Shutdown 3 node of Env.D~F while Case.A~ 

To : Shutdown (whatever) node. Delete contents from harddrive to simulate harddrive failure. 

and a new test
Restore test: Add previously broken node back into the cluster. 




Serial Thrilla wrote:
> Maybe we can add tests for the library too? :)
> 
> I bring it up because I've been having recent troubles with 
> glusterfs_fstat() and glusterfs_readdir().
> 
> Thanks
> Rob
> 
> Geoff Kassel wrote:
>> Hi,
>>    I'd also like to put my vote in for (more) regression tests - 
>> especially scripted/automated tests of the 'make test' variety which 
>> the public can use.
>>
>>    Given recent data integrity issues, this would help to instill 
>> confidence in GlusterFS releases by allowing users to test a new 
>> release build before putting it into use.
>>
>>    It would also allows users of more exotic environments (i.e. 
>> kernels with PaX or SELinux, Darwin, FreeBSD, etc) to determine 
>> exactly where their environments cause issues. This would make it much 
>> easier for the GlusterFS developers to maintain compatibility with 
>> these platforms.
>>
>> Kind regards,
>>
>> Geoff Kassel.
>>
>> On Fri, 27 Mar 2009, Kirby Zhou wrote:
>>> Maybe unit test is too difficult to add to existing code.
>>>
>>> I think the following classical cases should be considered integrated 
>>> into
>>> the whole suite regression test.
>>>
>>>
>>>
>>> 1.       Test Environments
>>>
>>> a)         4 nodes with DHT.
>>>
>>> b)         A with all performance xlators.
>>>
>>> c)         B with all feature xlators.
>>>
>>> d)         4*2 nodes with DHT and AFR.
>>>
>>> e)         D with all performance xlators.
>>>
>>> f)          E with all feature xlators.
>>>
>>> 2.       Test Case
>>>
>>> a)         Small file test. Build kernel or gcc or apache over Env.A-F
>>>
>>> b)         Big file test. Run iozone with file larger than 2G.
>>>
>>> c)         Huge file test. Construct some huge sparse file larger 
>>> than 2T.
>>>
>>> d)         Failover test. Shutdown 3 node of Env.D~F while Case.A~ 
>>> Case.C
>>> running.
>>>
>>>
>>>
>>> Thanks
>>
>>
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 
>> 270.11.29/2024 - Release Date: 03/26/09 07:12:00
>>
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel