Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-04-10 21:54+0100 Andrew Ross wrote: > > Hazen, > > That's interesting, and at odds with my tests a week or so back on Kubuntu > 14.10. Can you confirm which flavour and version of Ubuntu you are using? > Also, I assume this is with Qt4 and not Qt5? Hi Andrew: The answers to your question

Re: [Plplot-devel] Release status: call for comprehensive testing

On 04/10/2015 09:06 PM, Alan W. Irwin wrote: > On 2015-04-10 12:29-0400 Hazen Babcock wrote: > >>> >>> That's a fairly sparse but still acceptable comprehensive test result >>> for >>> this release, but to start the next release cycle properly I strongly >>> encourage everybody here to learn to r

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-04-10 21:54+0100 Andrew Ross wrote: > [Hazen's poor qt result is] at odds with my tests a week or so back on Kubuntu > 14.10. Hi Andrew: Could you please report the details of those good comprehensive test results at

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-04-10 12:29-0400 Hazen Babcock wrote: >> >> That's a fairly sparse but still acceptable comprehensive test result for >> this release, but to start the next release cycle properly I strongly >> encourage everybody here to learn to run the >> scripts/comprehensive_test.sh bash script to co

Re: [Plplot-devel] Release status: call for comprehensive testing

On 04/10/2015 04:54 PM, Andrew Ross wrote: > > Hazen, > > That's interesting, and at odds with my tests a week or so back on Kubuntu > 14.10. Can you confirm which flavour and version of Ubuntu you are using? > Also, I assume this is with Qt4 and not Qt5? > Andrew, This is what I have: hb ~$ unam

Re: [Plplot-devel] Release status: call for comprehensive testing

Hazen, That's interesting, and at odds with my tests a week or so back on Kubuntu 14.10. Can you confirm which flavour and version of Ubuntu you are using? Also, I assume this is with Qt4 and not Qt5? Andrew On Fri, Apr 10, 2015 at 12:29:15PM -0400, Hazen Babcock wrote: > > > >That's a fairly s

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-05 01:17-0700 Alan W. Irwin wrote: > On 2015-04-04 23:11-0700 Greg Jung wrote: > >> afaict these environment variables are essential for plots: >> >> PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers >> PLPLOT_HOME=/usr/local/share/plplot5.10.0/ >> >> DRV_DIR for dynamic loading, to ge

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-04 23:11-0700 Greg Jung wrote: > afaict these environment variables are essential for plots: > > PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers > PLPLOT_HOME=/usr/local/share/plplot5.10.0/ > > DRV_DIR for dynamic loading, to get the driver_info files (.dll files > are to be pick > u

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

afaict these environment variables are essential for plots: PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers PLPLOT_HOME=/usr/local/share/plplot5.10.0/ DRV_DIR for dynamic loading, to get the driver_info files (.dll files are to be pick up in PATH) and PLPLOT_HOME for support files: greg@Homerw

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-04 21:27- Arjen Markus wrote: > I had to suppress the test_interactive part as well as the traditional build, > but then it finished all right. See the attached tgz-file for the details. I agree that limited Cygwin result looks good (other than the test_interactive and traditional

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-04 19:34- Arjen Markus wrote: > Hi Alan, > > > >> -Original Message- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> Sent: Saturday, April 04, 2015 9:04 PM >> To: Arjen Markus >> Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list >> Subject: RE:

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Sent: Saturday, April 04, 2015 9:04 PM > To: Arjen Markus > Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list > Subject: RE: Release status: call for comprehensive testing: Cygwin >

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-04 15:31- Arjen Markus wrote: > Hi Alan, > > > >> -Original Message- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> >> @Arjen, Phil, and Jim: >> >> As release manager, that latter possibility of a regression in comprehensive >> testing >> on the Cygwin platfo

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > @Arjen, Phil, and Jim: > > As release manager, that latter possibility of a regression in comprehensive > testing > on the Cygwin platform really concerns me, and I ask at least one of you guys

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

Hi Alan, Greg, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > @Greg: You have much more experience with Cygwin than I do (since my actual > experience is zero). Nevertheless, historically there has been lots of > warnings on > the CMake list that Cygw

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-03 14:06-0700 Greg Jung wrote: > In Cygwin, I do use the cygwin cmake; but it isn't distributed by > cygwin, I built it from source. At one point I tried the windows > cmake from cygwin and it failed miserably. @Greg: Thanks for that clarification. I agree that cmake built on Cygwin

Re: [Plplot-devel] Release status: call for comprehensive testing: MinGW-w64/MSYS2

The cmake I specify for MSYS is a vanilla cmake downloaded from cmake.org; I use this because all of my other CMakes use scripts I modified. Cmake for Msys needs to use msys make, not mingw32-make; otherwise you want to do a mingw build which involves hiding "sh" from the PATH, using CMD.exe, etc

[Plplot-devel] Release status: call for comprehensive testing: wxwidgets

I have just finished (once again) a complete test of wxwidgets for all our standard examples. I have reported the results (which are quite encouraging) at the (re-edited) https://sourceforge.net/p/plplot/bugs/151/. It's this bug report I will refer to in the release notes. Freeze and release pro

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

In Cygwin, I do use the cygwin cmake; but it isn't distributed by cygwin, I built it from source. At one point I tried the windows cmake from cygwin and it failed miserably. On Fri, Apr 3, 2015 at 12:20 PM, Alan W. Irwin wrote: > On 2015-04-02 22:57-0700 Greg Jung wrote: > >> This is a long-stan

[Plplot-devel] Release status: call for comprehensive testing: MinGW-w64/MSYS2

On 2015-04-02 22:57-0700 Greg Jung wrote: > > In each setup there are naturally missing pieces. >> From my perspective,I need only libplplot.dll, libplplotcxx.dll, > wingcc, svg, ps, null, Z, X, and maybe cairo devices, and wxwidget. If > a failure occurs because it isn't within this narrow requir

[Plplot-devel] Release status: call for comprehensive testing: Cygwin

On 2015-04-02 22:57-0700 Greg Jung wrote: > This is a long-standing cygwin warning, "CMake no longer defines WIN32 > on Cygwin!" > for those rip-van-winkles coming back to cygwin and somehow wanting > WIN32 to be defined. > I am very familar with the possible quirks that can arise with Cmake; > if

Re: [Plplot-devel] Release status: call for comprehensive testing

] > Sent: Friday, April 03, 2015 7:57 AM > To: Alan W. Irwin > Cc: PLplot development list > Subject: Re: [Plplot-devel] Release status: call for comprehensive testing > > This is a long-standing cygwin warning, "CMake no longer defines WIN32 on > Cygwin!" > for those

Re: [Plplot-devel] Release status: call for comprehensive testing

This is a long-standing cygwin warning, "CMake no longer defines WIN32 on Cygwin!" for those rip-van-winkles coming back to cygwin and somehow wanting WIN32 to be defined. I am very familar with the possible quirks that can arise with Cmake; if there is a systemic failure it generally blows up in y

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-30 12:42-0700 Alan W. Irwin wrote: > There is a big warning in plplot-cygwin/output_tree/cmake.out (for > version 3.0.1) about "CMake no longer defines WIN32 on Cygwin!" Hi Greg: I believe I have now found the source of that warning message which is (according to cmake mailing list me

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-31 11:05-0700 Greg Jung wrote: > Here is tarball og the output directory from recent fully-completed > Suse-13.2 test. > I did terminate interactive testing at the end, by killing windows, > the strip chart was going very slow. But the wx Viewers looked great. > Hi Greg: Thanks very

Re: [Plplot-devel] Release status: call for comprehensive testing

Here is tarball og the output directory from recent fully-completed Suse-13.2 test. I did terminate interactive testing at the end, by killing windows, the strip chart was going very slow. But the wx Viewers looked great. On Tue, Mar 31, 2015 at 9:31 AM, Alan W. Irwin wrote: > On 2015-03-31

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-31 09:31-0700 Alan W. Irwin wrote: > Hi Arjen: > > Gack. I am really glad you found this bug in setting the -DUSINGDLL > compile flag for libplplotqt source files (and also for smoke > bindings) for the static library case. This bug was caused by a commit made > by me back in 2013. O

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-31 09:33- Arjen Markus wrote: > Hi Alan, > >> >> @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? >> >> There is a big warning in plplot-cygwin/output_tree/cmake.out (for version >> 3.0.1) >> about "CMake no longer defines WIN32 on Cygwin!" Have either of

Re: [Plplot-devel] Release status: call for comprehensive testing

Hi Alan, > > @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? > > There is a big warning in plplot-cygwin/output_tree/cmake.out (for version > 3.0.1) > about "CMake no longer defines WIN32 on Cygwin!" Have either of you run into > this > issue for CMake on Cygwin? The

Re: [Plplot-devel] Release status: call for comprehensive testing

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? > > There is a big warning in plplot-cygwin/output_tree/cmake.out (for version > 3.0.1) > about "CMake no longer defines

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-30 12:14-0700 Alan W. Irwin wrote: > On 2015-03-30 10:40-0700 Greg Jung wrote: > >> Here are gzipped- tar files sent separately because the list >> filters may kill the message altogether. > > Our mailing list does not kill tarballs in my experience. So to test > that in this case, I a

Re: [Plplot-devel] Release status: call for comprehensive testing

Mingw/msys: Because I have cmake modified to look in /usr/local and such for libraries and such (not a good idea, I know now), I added the option --cmake_command to the script and used --cmake_command=/d/path-to-cmake/bin/cmake.exe and the make completed ok but the ctest hung at example/c/x00c;

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-26 18:50-0700 Alan W. Irwin wrote: > With commit id 5f6e28f I finally have been able to complete > scripts/comprehensive_test.sh on Linux without issues which removes > the last known regression compared to 5.10.0 for this release which is > a much-desired result. > > My next steps are

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-28 22:20-0700 Alan W. Irwin wrote: > Also, when you report back again, will you please always specify the > scripts/comprehensive_test.sh options you used in every different > platform case? The easiest way to do that is to always include > everything output from the script rather than

Re: [Plplot-devel] Release status: call for comprehensive testing

> On Mar 29, 2015, at 9:17 AM, Andrew Ross > wrote: > > Also -np to prevent pausing between > pages doesn't work. This is not a major issue, but is a slight pain when > running the automatic tests. > > Andrew I believe this bug might be related to the extra plP_eop() call. This results

Re: [Plplot-devel] Release status: call for comprehensive testing

On Sat, Mar 28, 2015 at 05:41:12PM -0700, Alan Irwin wrote: > On 2015-03-28 21:40- Andrew Ross wrote: > > I use 2.2.1 as well but with additional patches applied. > > See cmake/epa_build/libharu/CMakeLists.txt for how to locate those > patches. > > Most of those are to install a CMake-based

Re: [Plplot-devel] Release status: call for comprehensive testing

Hi Greg: It's important our interchanges remain on list so others can benefit from them so please don't drop the list Cc from your replies. Thanks for all these test results. More below in context On 2015-03-28 16:27-0700 Greg Jung wrote: > HI Alan, > > I did use make all on that run, but pro

Re: [Plplot-devel] Release status: call for comprehensive testing

On 2015-03-28 21:40- Andrew Ross wrote: > On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote: >> >> Alan, >> >> For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh >> fails. Compile all goes fine, but the test of the C examples with the pdf >> driver fails at examp

Re: [Plplot-devel] Release status: call for comprehensive testing

On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote: > > Alan, > > For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh > fails. Compile all goes fine, but the test of the C examples with the pdf > driver fails at example 24 with > > ERROR: error_no=1050, detail_no=0 >

Re: [Plplot-devel] Release status: call for comprehensive testing

On Thu, Mar 26, 2015 at 06:50:22PM -0700, Alan Irwin wrote: > On 2015-03-25 14:30-0700 Alan W. Irwin wrote: > > >> 2. Because of issues like the qt_example segfault that I have just > >> fixed, I have as yet been unable to complete a comprehensive test of > >> PLplot on Linux. Until I can get suc

[Plplot-devel] Release status: call for comprehensive testing

On 2015-03-25 14:30-0700 Alan W. Irwin wrote: >> 2. Because of issues like the qt_example segfault that I have just >> fixed, I have as yet been unable to complete a comprehensive test of >> PLplot on Linux. Until I can get such a clean test the possibility >> exists there are other such segfault