Hi Chris: I recently updated the paratest.server script so the default timeout is "never". Does that help? I don't think there's a blacklist feature, but you can add a skipif file in your workspace. If there's an environment variable that paratest.server sets uniquely, you could key off of that to allow the test to run under start_test. Even with a skipif file, the test will run if you call it out explicitly: start_test TooManyThreads.chpl .
HTH, THH ________________________________ From: Chris Wailes [[email protected]] Sent: Thursday, March 27, 2014 10:15 AM To: [email protected] Subject: [Chapel-developers] Paratest and TooManyThreads.chpl Recently, when I try and run the test suite on my machine using paratest.server the script will timeout when running the TooManyThreads.chpl test and cause the test suite to stop. This isn't a problem when I run one test at a time. Is there a way to scale back the number of threads that are deemed to be "too many" when running multiple tests at once, or to blacklist this test when running the suite through paratest.server? - Chris
------------------------------------------------------------------------------
_______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
