On 2010-03-04 16:25-0800 David MacMahon wrote: > Hi, Alan, > > On Mar 3, 2010, at 12:05 , Alan W. Irwin wrote: > >> time make -j4 -k test_noninteractive >& make_testnoninteractive.out > > I'm trying to run this test now, but I'm not sure what to expect nor how to > interpret the results I get. It ends with an error message for me using > either svn/trunk or my plf2ops changes. At least they appear to be the same > errors! :-) Amidst the output I get this... > > c++ > Missing examples : > Differing postscript output : > Missing stdout : > Differing stdout : > f77 > Missing examples : > Differing postscript output : > Missing stdout : > Differing stdout : > f95 > Missing examples : > Differing postscript output : > Missing stdout : > Differing stdout : > java > Missing examples : > Differing postscript output : > Missing stdout : > Differing stdout : > octave > Missing examples : 19 > Differing postscript output : 28 29 > Missing stdout : > Differing stdout : 14 > tcl > Missing examples : > Differing postscript output : 21 28 > Missing stdout : > Differing stdout : 21
Those are the expected results. The "glass is 99.6 per cent full" way to look at this is 99.6 per cent of our bindings/examples produce identical PostScript results to our C versions which is a terrific achievement. On my own Linux system I confirm the above except I get good results for octave example 29. Note, I have octave-3.0.1 installed, and in the past we have found our octave interface sometimes had version mismatch troubles with other versions. I also have a fully loaded installation so I also have some additional results: ada Missing examples : Differing postscript output : 28 29 Missing stdout : Differing stdout : adathick Missing examples : Differing postscript output : 28 29 Missing stdout : Differing stdout : ocaml Missing examples : Differing postscript output : Missing stdout : Differing stdout : lua Missing examples : Differing postscript output : Missing stdout : Differing stdout : d Missing examples : Differing postscript output : Missing stdout : Differing stdout : (I have edited out a differing example 25 for all my bindings because I am currently testing a variation of that C example which is not mimicked by the rest of the example 25 implementations.) The net result of anything to the right of the colons is a non-zero return code which generates the make error you observed at the end. So I would count your test_noninteractive results as a roaring testing success so long as there were no _other_ errors mentioned in the make_testnoninteractive.out file. > > I get the feeling that I shouldn't have any numbers to the right of the > colons. It also seems like this build some of the tests, so I think I should > run it several times, discard the times from the first run and average the > rest. Actually, I wouldn't worry too much about the timing. It is a really coarse measure in any case since lots is involved other than your changes. For example, the 17th standard example always takes a long time to run. The timing results are just a sanity check that some example doesn't start taking orders of magnitude more time. A much better check is to run one well-picked example (as you have already done). > > I ran make test_interactive, but it gets to... > > [ 97%] Built target test_c_xcairo > [100%] Built target tk > Generate C results for tk interactive device > Testing subset of C examples for device tk > x01c > > ...and then appears to hang there. I get an empty plserver window, but don't > know what to do at that point, so I wait a while and then ctrl-c which stops > the test sequence. > > Any pointers? Hmm. That sounds suspiciously like one of the -dev tk errors that appears to be recently fixed for the Linux platform. If you want to help us by pursuing that further, then what are the results of examples/c/x01c -dev tk after "make all"? Note, the "no plot" is the issue. If you get a plot, then simply hit the enter key to exit from the -dev tk GUI. Whatever messages you get in that case (if is is not a hang with no message) you should also be able to see (mixed in with everything else) in make_test_interactive.out. However, you may want to put this Tk issue aside (-DENABLE_tk=OFF -DPLD_tk=OFF) for now and instead concentrate on testing your 2D patch for the non-Tk case now so we can move forward with that. Your choice as to what you do first. Either would be quite a help to us. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
