On 2015-04-04 15:31-0000 Arjen Markus wrote: > Hi Alan, > > > >> -----Original Message----- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> >> @Arjen, Phil, and Jim: >> >> As release manager, that latter possibility of a regression in comprehensive >> testing >> on the Cygwin platform really concerns me, and I ask at least one of you >> guys to >> confirm/deny that possibility by simply running >> scripts/comprehensive_test.sh on >> Cygwin with appropriate environmental variables set (ideally with a "source" >> script that you run from using the bash "source" command to keep everything >> easily >> and automatically reproducible) to setup the Cygwin platform for the PLplot >> build and >> test. >> >> N.B. I emphasize sourcing a "source" script from bash and running >> scripts/comprehensive_test.sh as opposed to piece-meal tests done by hand >> since >> (a) the script result should be completely automated and reproducible if you >> have set >> up the platform properly, and (b) comprehensive testing is so much more >> powerful >> than piece-meal tests. >> So I would appreciate hearing from any of you quickly if you are in a good >> position to >> run that script. >> > I ran scripts/comprehensive_test.sh with no argument and prepending two > directories to the PATH environment variable (.../shared/bin and > .../shared/lib/plplot5.10.0/drivers) and everything ran until the > "traditional make" step, see the attached output. The error seems to be > specific to Cygwin - the names of the libraries. > > The other steps did not reveal any problems, as far as I can tell from an > examination of the output files.
Hi Arjen: It is very encouraging from my release manager perspective that all components of PLplot that you have enabled on Cygwin appear to be working for the shared case so long as you exclude the traditional build of the installed examples. From the output that you attached it appears a number of different things went wrong with that traditional build and test of the installed examples. We can address those post-release. For now, please continue the process before this release deadline by using the appropriate documented arguments of scripts/comprehensive_test.sh until you get a complete run of the script with no errors. Then we will know where we stand, i.e., exactly which parts of the comprehensive test work on Cygwin and which do not, and we can post those definitive results on our wiki and refer to them in the release notes. The required documentation of the script is found by using the --help argument, and it follows from that and the number of bad results you obtained for the make + pkg-config traditional build of the installed examples that you should re-run the script using the arguments "--do_test_traditional_install_tree no". Hopefully, that will be enough to give you a clean result, but if not, please continue by re-running the script with more removed from the tests. Once you have a clean result please post all relevant results here (i.e., attach a compressed version of the output from the script, and also attach a compressed tarball of _just_ the directories comprehensive_test_disposeable/shared/output_tree comprehensive_test_disposeable/nondynamic/output_tree comprehensive_test_disposeable/static/output_tree) so I can use those data to summarize the good and dropped part of your comprehensive test on the wiki. @Greg This (mostly) good result from Arjen on Cygwin obviously is sharply in contrast with your own results where not even ctest worked on that platform. Therefore, I suggest you get in touch with Arjen to figure out exactly what he did. Then following that procedure rigourously should give you similar good results, and probably even more importantly we should be able to document exactly what you did that should be avoided by others on Cygwin when they are running scripts/comprehensive_test.sh. 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 __________________________ ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
