It's been one more day of chasing rpath (and other) issues. I was able
to obtain a good comprehensive test result for a normal build environment
(after some work dealing with some issues that had crept in since
I successfully ran this test ~10 days ago), but there continue to
be issues for the epa_build environment cases. So the following
paragraph is still true....
On 2013-12-15 16:45-0800 Alan W. Irwin wrote:
> So the release continues to be delayed by issues I have been
> discovering as a result of trying comprehensive testing for the
> epa_build environment.
IMPORTANT: Also, I have made so many build-system changes since you
guys last tested, this is advance notice that later this week after
all my tests are done (including the currently non-working or
non-tested epa_build environments for both Linux and MinGW/MSYS), I
will call on as many of you as have time for it this close to the
Christmas season to do one last round of testing on your own
platforms/build system environments before I release.
The reason this additional testing is important is my recent results
show that comprehensive tests can sniff out build-system bugs much
better if applied for a wide variety of build environments i.e., cmake
options, environment variables, buildtools that have been built,
dependencies that have been built, and system libraries that are
available. There are a very large number of different build
environments even on Linux so it is not realistic to expect testing on
just one them is going to be sufficient. In fact, when I recently
switched from my usual Linux build environment to three different
Linux build environments (my usual one and two different
("build_plplot" and "build_plplot_lite") epa_build build environments,
those tests found a whole host of build-system issues I was unaware of
before, and which I am currently fixing. If we add in your different
Linux build environments and also different build environments on
other platforms, the sensitivity of the group of comprehensive tests
from all of us becomes even greater.
Note in contrast to the need for large amounts of testing for each
release cycle, it is also quite important to release in a timely
manner. So it's a somewhat arbitrary balancing act between the two
needs depending on the release manager's tastes. In my own case, I am
going to wait until all my own tests work, and as soon as that happens
(now probably Wednesday at the earliest), I will let you know and give
you a chance to do some final testing while I take a day or so to go
through the release process (version changes, building the website,
etc.). Thus, I do hope some of you will be mentally prepared by this
advance notice to test on short notice this week when I give the word.
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
__________________________
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel
