This is directly not only to Arjen, but also to everybody else here who wants to help out with comprehensive testing for this release.
On 2016-12-13 11:49-0000 Arjen Markus wrote: > Hi Alan, > > > >> -----Original Message----- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> Sent: Tuesday, December 13, 2016 12:13 PM >> >> I am very happy to hear that. Big sigh of relief! >> >> Since I currently have comprehensive test success on Linux and you now also >> have >> that on Cygwin, would you be willing to follow up with a comprehensive test >> on >> MinGW-w64/MSYS2 and your spot checks on MSVC with ifort? >> > Sure, that should be no particular problem. > @Arjen: Great. I should have emphasized you should drop all constraints for these comprehensive tests other than the ones that have proved absolutely necessary in the past for the given platform. So ideally your script launch (aside from the nice part, see below) should be scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no with very few if any further constraining options. @Everybody: I have specified the --do_submit_dashboard yes option here. For a normally unconstrained comprehensive test on a given platform, that will submit 3 separate dashboards (for the ctest results for the shared + dynamic devices case, the shared + nondynamic devices case, and the static + nondynamic devices case), and you should be able to see that subset of the comprehensive test results at <http://my.cdash.org/index.php?project=PLplot_git>. But I ask you to also send me the report tarball as well (normally stored at ../comprehensive_test_disposeable/comprehensive_test.tar.gz) both when the script fails to complete (so I can help you figure out the problem or disable the non-working parts of PLplot on your platform so the script completes) and when the script completes (so I can summarize your complete results with your permission at <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing@20Reports>). I presume most testers here do want to skip the interactive part of the comprehensive tests because X is so slow on Cygwin, and if you do decide to go ahead with the interactive part of the tests on platforms where X is fast, then I should warn you there is a whole lot of keyboarding and mouse clicking to get through to finish the interactive part of the comprehensive test. For myself, I tend to use --do_test_interactive no a lot for these reasons, but I do drop this option (or specify the equivalent --do_test_interactive yes) several times during a release cycle to make sure the interactive part of PLplot is working properly. But very few others need to put themselves through that boredom unless and until they are highly motivated to test PLplot interactive capability on their particular platform. @Arjen: This request for more comprehensive tests is for both MinGW-w64/MSYS2 and Cygwin (since the successful test you completed just now for that platform was constrained just to be the build-tree ctest test for the shared library + dynamic devices case). These requested comprehensive tests should be pretty straightforward for you to do since your launch script where you specify the platform setup (set environment variables, etc. and the comprehensive test options) should be completely automated by now in the interest of repeatability. So all you should really have to do is sit back and let your computer do all the work. @Everybody: A tip for Unix users here is to run these comprehensive tests as follows time (nice -19 scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no ) The time part of this lets you know how much time this took once the command finishes. The nice -19 part forces this comprehensive test to only use the cpu if you don't need it for something else. So when I do the above, my computer feels somewhat slower (because of all the disk i/o going on with these tests and the mememory used by these tests), but the computer is still quite usable. If I don't specify nice as above, then the computer seems very slow during these tests. @Arjen: It appears the "nice" command does exist on Cygwin. So I suggest you try the above trick as well in your launch script to see if it helps you to use your computer for other tasks during these tests. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
