On Wed, Dec 18, 2013 at 09:35:52PM +0000, Andrew Ross wrote:
> On Wed, Dec 18, 2013 at 09:06:53AM -0800, Alan Irwin wrote:
> > To Andrew, Jerry, Arjen, and Phil:
> > 
> > There are some important questions below for you. I need those
> > questions answered for the release notes (README.release) for the
> > forthcoming release.
> > 
> > For example, when I am done with my testing, my test summary
> > in README.release will read
> > 
> > Comprehensive tests for a complete system build environment were run
> > on 64-bit Debian Wheezy Linux on AMD-64 hardware.
> > 
> > Comprehensive tests for a limited (qt, cairo, and wxwidgets PLplot
> > components were dropped) epa_build environment were run on 64-bit
> > Debian Wheezy Linux on AMD-64 hardware.
> > 
> > Comprehensive tests for a complete epa_build environment were run
> > on 64-bit Debian Wheezy Linux on AMD-64 hardware.
> > 
> > Comprehensive tests for a limited (qt, cairo, and wxwidgets PLplot
> > components were dropped) epa_build environment were run for 32-bit
> > MinGW/MSYS/Wine on AMD-64 hardware.
> > 
> > I need similar tests summaries from all of you that have run tests for
> > this release.  I give preliminary (and quite uncertain, see all the
> > question marks) versions below.  Please send back the corrected
> > versions of these test summaries.  In most cases the question marks
> > should be quite easy to replace with your actual test data.  However,
> > the phrase "Limited tests??" is a bit of a special case.  It should be
> > replaced by one of "Comprehensive tests" (if you actually ran the
> > scripts/comprehensive_test.sh script), a phrase summarizing the exact
> > test you ran such as "ctest + the test_noninteractive target in the
> > build tree" for intermediate testing, or "Limited tests" for those
> > cases where you actually only did a few tests by hand.
> > 
> > @Andrew:
> > 
> > Limited tests?? for a complete system build environment were run
> > on 64-bit?? Debian unstable on AMD-64 hardware??
> 
> I ran make test_noninteractive and test_interactive for a complete system 
> build environment on a 64-bit Debian unstable system on AMD-64 hardware. 
>  
> > Limited tests?? for a complete system build environment were run
> > on 64-bit Ubuntu version?? on AMD-64 hardware?
> 
> I ran make test_noninteractive and test_interactive for a complete system
> build environment on a 64-bit Ubuntu Saucy (13.10) system on AMD-64 
> hardware.
> 
> I did not get chance to run the tests on 32-bit Debian unstable with 
> AMD-64 hardware (though I can using the same pbuilder setup used to test 
> Debian 64 bit)

I've now also run the scripts/comprehensive_test.sh test on my Ubuntu 
system. I encountered some problems in that on several occasions, 
without warning, by kde session died. It was not reproducible, but in 
each case it was while running the test_interactive tests, mostly in 
the install tree. I've never seen this when running the test 
individually in serial so I don't know whether it is a parallel build 
problem or some hardware problem.

Eventually I managed to get through almost all the tests though. The 
only issue I encountered was a segfault with the C++ qt_example for the
nondyndriver case. Valgrind shows an invalid call to free / delete and
a memory access violation. The shared case is fine with valgrind so I 
assume it is something about the static drivers.

For the fully static case I do not get a segfault, but valgrind shows a 
load or invalid reads in wx libraries ?!?

Alan, do your tests reproduce this? I'll try a debug build to see if I 
can get to the bottom of it.

Andrew

------------------------------------------------------------------------------
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

Reply via email to