Hi Chris, I am now figuring out what to change in order to run megatests. Due to recent fixes and updates, old megatests are not working. I have to throw away some old parts.
Yours, Namshin Kim On Sun, Sep 14, 2008 at 6:19 AM, Christopher Lee <[EMAIL PROTECTED]> wrote: > > Hi, > Namshin's recent problem with running out of memory reminds me that > our testing may not emphasize sufficiently one major aspect of Pygr, > namely scalability. We have written a number of "megatests" that test > scalability, but I'm not sure whether they're included in Titus' > nightly tests. (megatests are tests that take too long or require too > much data or resources to be included in the normal test suite. Their > purpose is both more rigorous usage testing, but also scalability > testing). Namshin used to run them nightly in my lab, but I'm not sure > whether that test automation is still running. I've never gotten any > test reports from it... > > We shouldn't be dependent on users reporting scalability problems. > Instead, we should have megatests that will automatically tell us > (hopefully within a day) if we have screwed up some basic aspect of > scalability. > > Titus, Namshin, what are your thoughts on this? > > Yours, > > Chris > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
