To everyone here:

The actual date of the release is still uncertain because I am not
completely done with my planned comprehensive MinGW/MSYS testing yet.
However, I have been having good luck with comprehensive testing on
Linux, so now (revision 12980) would be a good time to repeat the
tests (currently documented in README.release) that a lot of you did
for the last release.

The plplot_lite epa_build with ENABLE_COMPREHENSIVE_PLPLOT_TEST=ON
(and with interactive parts of the test turned off locally to speed up
the test) goes through with complete success on the Linux platform
showing there are no regressions introduced by the build system
changes since the previous good test results for this platform. Note,
as indicated by the ENABLE_COMPREHENSIVE_PLPLOT_TEST name, this test
is a comprehensive noninteractive one that is done with
script/comprehensive_test.sh. This test took roughly half an hour on
Linux.

On top of that epa_build regression check for the Linux platform, I
have successfully completed some critical bits and pieces of the same
comprehensivive plplot_lite tests on MinGW/MSYS/Wine that were failing
for the last release.  That leads me to believe a repeat on that
platform of the comprehensive test described above for Linux is likely
to succeed.  I have therefore initiated such a test ~5 hours ago, and
it is still going strong with no run-time errors.  If that success
continues, then from the time it has taken to do individual parts of
the comprehensive test, I think the whole thing will finish roughly 15
(!) hours after the start which is a Wine slowdown of a factor of
roughly 30 compared to the equivalent Linux test.  As I have remarked
before, that slowdown is due to the peculiarly large command startup
latency for Wine multiplied by the ~10^5 commands that occur in this
comprehensive test.  This huge latency slowdown should not occur for
any other Windows platform and certainly not for any non-Windows
platform.

As of revision 12980 I have also updated the epa_build directions in
cmake/epa_build/README to be consistent with my latest comprehensive
testing experience with epa_build.

Therefore, this is a good time for anybody here interested in
doing comprehensive testing to follow those instructions.

@Andrew: note the degree of parallelism is now kept at -j4 rather than
-j8 so some of the X issues you had with large numbers of interactive
tests going on simultaneously on one of your platforms might be gone
this time.

@Arjen: This would be a good time for you to attempt to adapt the
directions in the above README file for the MinGW/MSYS/Wine case in
order to replicate my current test on your MinGW/MSYS/Microsoft
Windows platform.  I think the Microsoft Windows command startup
latency will be considerably less than the Wine case so the timing
should be much reduced compared to the Wine case and roughly the same
as the Linux case, i.e., roughly an hour. So if you start on this
right away and don't have any trouble figuring out my directions, it
is possible you could finish this test before I do.  :-) Of course, I
am pretty sure this is the first time you have attempted to do such
comprehensive tests of PLplot so it is more likely that you will run
into some trouble, but I would be more than happy to help you with
that if it occurs.

For the initial stages of getting this to work, I suggest you first
try building just a few of the -DBUILD_THE_BUILDTOOLS=ON projects. But
if all goes well (indicating you have set up the required environment
variables correctly and your downloaded MinGW and MSYS have been
installed correctly) you should be able to build all of them.
(Note, this lack of caution is allowed because I have already gotten
rid of most/all of the MinGW/MSYS epa_build issues.  But, of course, you
would want to proceed more cautiously for the Cygwin case where
there are likely to still be epa_build issues.)

The other deviation from the official instructions, is I suggest you
temporily drop the interactive part of the -DBUILD_THE_BUILDTOOLS=OFF
-DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON test case (as I am doing for my
long MinGW/MSYS/Wine test above).  This can be done by locally editing
cmake/epa_build/plplot_lite/CMakeLists.txt to replace the first "echo
yes" that occurs in that file by "echo no".

Anyhow, good luck with your MinGW/MSYS testing.

@Everybody:

Assuming the comprehensive noninteractive MinGW/MSYS/Wine test described above
finishes for me without errors, then the last thing I plan to do for
this release cycle is to repeat this comprehensive test both for Linux
and MinGW/MSYS/Wine for the interactive test case.  In addition, I
assume some of my time before the release will also be consumed by
attempting to deal with errors that others find through their own
testing.  For those reasons the actual date of the release is still
uncertain, but with luck it might be as early as the middle of next
week.  But given a choice between fixing some obvious error one of you
finds or doing the release regardless to meet some arbitrary deadline,
I will do the former. So I look forward to seeing lots of test
reports from you guys!  :-)

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
__________________________

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to