Re: [Plplot-devel] Linux testing

[Pedro V. <ped...@sp...>]

@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

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?


3)

On another Linux, 16.04,  where *I don't* have gfortran

cmake ..  -G "Unix 
Makefiles" -DCMAKE_INSTALL_PREFIX:PATH=/home/pvn/plplot-install -DCMAKE_BUILD_TYPE=Debug 
  -DBUILD_TEST=ON -DPLPLOT_WX_DEBUG_OUTPUT=ON
make VERBOSE=1
make VERBOSE=1 test_wxPLplotDemo

Infinite loop
22:25:42: Debug: Plot() Yielding

pvn@server:~/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" --do_test_noninteractive 
no --do_ctest no

then it stays here (I suppose because of the infinite loop)
and I get a blank plviewer window

Each of the steps in this comprehensive test may take a while....
cmake in the build tree
make -j4 VERBOSE=1 test_interactive in the build tree

4)

results for my patch commit

@Phil
I was able to make the example 01 run with no runtime errors by 
re-introduncing the OnCreate() event (but also keeping the Create() call).
But then I got other errors.
I am not sure what are the consequences of these changes, so here it's 
better for me to wait until you provide some insight into this.

to do items:

1)

it would be great if any of you could reproduce my test_wxPLplotDemo 
behavior on Linux

the response from the developer


> This is not completely unexpected, the window is only really created when
> it's "realized" in GTK+/X11 terms, which can take quite some time, in
> particular if a remote X server is used


could this "remote X server is used" be because I am accesing my linux 
machines remotely ? (by using X2Go)


2)

maybe put the master back with one of the workarounds that I don't have the 
infinite loop,
so that I have a better idea of what happens in the comprehensing testing?

-Pedro

----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>; "Phil Rosenberg" 
<p.d...@gm...>; "PLplot development list" 
<plp...@li...>
Sent: Friday, December 23, 2016 5:19 PM
Subject: Re: [Plplot-devel] Infinite Yielding issue


> On 2016-12-23 16:43-0500 Pedro Vicente wrote:
>
>> by the way, what are the commands to do comprehensing testing?
>
> That script should be able to run on all Unix systems and Unix-like
> systems (i.e., Cygwin and MinGW-w64/MSYS2), but not currently for MSVC
> ("raw Windows").  However, Arjen plans to investigate a possibility for
> running that script on MSVC platforms as well in 2017.
>
> So for now, on Unix or Unix-like systems, I suggest you run
>
> 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" --do_test_noninteractive 
> no --do_ctest no
>
> I used exactly those options recently myself.
>
> Those options are constraints on the script to keep it from doing
> time-consuming (several hours?) tests that you probably don't
> need/want to run right now.
>
> So my suggested options constrain the script to just test the
> plplotwxwidgets library and the wxwidgets device driver for our 3
> major configurations and 3 different build trees. (So you will see the
> tests repeat 9 times for those combinations.) There are no
> noninteractive tests of the wxwidgets device driver or plplotwxwidgets
> library.  But to avoid the non-interactive C++ tests, we further
> constrain the script above to avoid all the non-interactive testing.
>
> As a result of these constraints the script just builds the
> test_interactive target for our 9 combinations.  For each of those
> combinations, that target in turn depends on test_wxPLplotDemo (to
> test the plplotwxwidgets library) and test_c_wxwidgets (to test the
> wxwidgets device driver).  You can also reduce the combinations if you
> like using additional constraint options for the script.
>
> Run
>
> scripts/comprehensive_test.sh --help
>
> to see about those further possibilities if the 9 combinations turn
> out to be too much.  :-)
>
> 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
> __________________________
>