> Thanks for your feedback. I'll work on this. I still need to figure out > how to run all the tests, but I'm sure there's a README somewhere if I look.
If you run util/start_test from anywhere under the test/ directory, it'll walk and test the entire directory tree under there, printing a summary at the end (and storing both log and summary in the test/Logs/ directory). Testing test/release/examples is usually a good starting point because it's (a) a small subset of the whole test system and (b) a collection of high priority tests (that also tend to touch a lot of the features in the langauge). Running the whole test suite takes a lot of time on a conventional system, so in practice we typically run in parallel using a script called paratest.server that calls into start_test. In some cases, you can prevail on someone within the Cray team to run the tests for you if you don't have the resources to do it in a timely manner (and have good confidence that things are working based on passing test/release, for example). See doc/developer/bestPractices/TestSystem.txt for more details about the testing system and the comments at the top of start_test for even more. -Brad ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
