Hi Pedro: It sounds like you might have some spare time now where you are willing to help us with comprehensive testing while you wait for Phil to comment about the wxwidgets errors you are now getting with your tentative change. So I assume you have that time below, But, of course, fixing that release-critical wxwidgets error is the top priority so you should drop comprehensive testing as soon as he responds.
More below about comprehensive testing. On 2016-12-23 22:44-0500 Pedro Vicente wrote: > > @Alan > > I changed the thread tittle, because I have all kinds of weird results on my > comprehensing testing. > > first the obvious: > > items 1) to 3) below are for the master branch > > 1) a Fortran error on Ubuntu 14.04 > > this was a simple > cmake .. -G "Unix Makefiles" > -DCMAKE_INSTALL_PREFIX:PATH=/home/pvicente/plplot-install > -DCMAKE_BUILD_TYPE=Debug -DBUILD_TEST=ON > make VERBOSE=1 >& make.txt > > but it detected gfortran and tried to build the fortran code. > output is attached You need to capture and look at your cmake output to confirm this, but if I am recalling another report correctly, Ubuntu 14.04 installs a three-year-old version of gfortran that is below our minimum supported version (see README.release) of 4.9.2. Which is why you have to disable fortran on that platform. > 2) > > then I disabled Fortran > > cmake .. -G "Unix Makefiles" > -DCMAKE_INSTALL_PREFIX:PATH=/home/pvicente/plplot-install > -DCMAKE_BUILD_TYPE=Debug -DENABLE_f95:BOOL=OFF -DENABLE_tcl:BOOL=OFF > -DENABLE_tk:BOOL=OFF -DBUILD_TEST=ON > make VERBOSE=1 > no errors > > then (note , running from the build location) > > pvicente@glace:~/plplot-plplot/build$ ../scripts/comprehensive_test.sh > --cmake_added_options "-DDEFAULT_NO_DEVICES=ON -DPLD_wxwidgets=ON > -DDEFAULT_NO_BINDINGS=ON -DENABLE_wxwidgets=ON -DENABLE_cxx=ON > -DPLPLOT_WX_DEBUG_OUTPUT=ON -DPLPLOT_WX_NANOSEC=ON -DENABLE_f95:BOOL=OFF" > --do_test_noninteractive no --do_ctest no > > Each of the steps in this comprehensive test may take a while.... > cmake in the build tree > ERROR: cmake in the build tree failed > > How can I capture the output here? It asks for a interactive (yes/no), can I > disable this and instead redirect the output to a file? First some background on that script. It is completely independent of what you do in your build tree (because it creates its own build tree and runs cmake there itself). So you did not have to run cmake first or locate yourself in the build tree. In fact, normally it is more convenient to run the script from the top-level directory in your source tree (although that is not a necessity). The script collects all of its work in its own directory tree whose top-level directory is by default ../comprehensive_test_disposeable _always expressed relative to the top-level directory of the source tree_. I assume from now on you run that script without specifying a prefix which always gives the same default location for scripts results no matter where you run the script from. All the outputs of all non-trivial commands the script runs are typically stored in ../comprehensive_test_disposeable/*/*/output_tree/*.out Normally I need all those files (and other information) to help you with comprehensive test results. Therefore the script collects that information in the report tarball which is stored in ../comprehensive_test_disposeable/comprehensive_test.tar.gz. So for each such comprehensive test you run, you should normally send me that report tarball if you cannot figure out the issue yourself by looking over the various *.out files that are collected as above. But this is not a normal case because you _know_ that a comprehensive test of wxwidgets is going to fail (because there are still issues with your present update that you need help from Phil to fix). So there is not much point to testing wxwidgets this way until you and Phil have the definitive fix. Meanwhile, while waiting for Phil, if you want to just help with systematic comprehensive testing, then I suggest you do that by dropping both fortran and wxwidgets as follows (assuming you run this from the top-level directory of the source tree). time (nice -19 scripts/comprehensive_test.sh --cmake_added_options "-DENABLE_f95=OFF -DPLD_wxwidgets=OFF -DENABLE_wxwidgets=OFF" --do_test_interactive no) This will drop all interactive testing (so you won't have to babysit this long test) and drop Fortran and wxwidgets for the reasons stated, but otherwise give PLplot a useful complete noninteractive test on Ubuntu 14.04. (The time and nice parts keep track of the total time required [likely several hours] and also give this script the lowest priority so you can carry on with that machine without completely locking it up while running this script). And if the script errors out for some reason, please look in the relevant *.out file and keep a brief note of those reasons, e.g., "gfortran 4.8.? had a build error" if you had attempted a comprehensive test on Ubuntu 14.04 without disabling fortran. Keeping track of those reasons helps me to enter appropriate footnotes at <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>. Anyhow, after each such script failure, run it again with other added options to turn off the relevant component of PLplot that is causing the failure. Once the script successfully finishes send me that report tarball, and I can use that information (assuming I have your permission) and your brief notes about which components failed to put one more much appreciated entry into the above wiki table of such comprehensive test results. > 3) > > On another Linux, 16.04, where *I don't* have gfortran > Actually, for 16.04 it would be useful if you installed fortran and included it in the comprehensive test (while still dropping wxwidgets) because that two years younger Ubuntu version than 14.04 should easily satisfy our minimum gfortan version requirement. And once you have the definitive fix for wxwidgets, then it should be completely straightforward to comprehensively test _just_ that component as I first suggested. I won't respond to the rest of your post because I believe only Phil can answer those wxwidgets-related questions. 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 __________________________ ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
