Re: [Plplot-devel] Next steps for comprehensive testing on Cygwin

[Arjen M. <Arj...@de...>]

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
>
> My detailed look showed everything was fine for the limited number of PLplot
> components tested other than the remaining issue with the "CMake no longer
> defines WIN32 on Cygwin!" warning which _should_ be fixed now, see my previous
> "humbled" post today on that subject.
>
I have not kept record of the number of times I thought a small change in a program did not mean I had to test it again :).

> I have now summarized the good results of your Cygwin comprehensive testing at
> <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>.
>
Great, especially as you have also listed the missing components. Cygwin may or may not provide all of them, but you already checked that :). This overview greatly reduces my task.

> So the question I want to address now is where should you go from here for
> comprehensive testing on Cygwin, i.e., which of the (B), (D), (E'), (F''), (G), and (H)
> remaining issues noted in that above summary should receive priority?
>
> There is obviously still something wrong with using your X server on Cygwin, but I
> suggest your address that issue last, i.e., keep running the comprehensive test with
> the "--do_test_interactive no" option not only because of that X server issue, but also
> because interactive comprehensive testing is much more difficult. (I have reduced
> that interactive testing misery as much as possible by using the -np [i.e., no pause
> between pages] option for all interactive tests, but -np does not work properly yet for
> Tcl/Tk nor wxwidgets so some babysitting misery is still inevitable if you do not use
> the "--do_test_interactive no" option.)

What I have noticed is that the configuration step looks for an X server with display name "localhost:0.0" but on Cygwin this is ":0.0" (don't ask me why). A workaround could be to set the DISPLAY variable beforehand.

Despite the configuration not finding the X server, it does allow building the X Window driver, which seems a wee bit odd.

>
> So that puts dealing with (B) (dropped interactive tests) last, and I suggest instead
> you deal with most of (D), (E'), (F''), (G), and (H) by simply increasing the scope of
> your comprehensive testing (and adding major functionality to your Cygwin PLplot
> platform) by installing all possible PLplot prequisites before you do your next
> comprehensive test.
>
> So to help you with that installation task I did some research,

Much appreciated.

> Installation of these packages and my fixes for any issues you find with that
> broadened scope of comprehensive testing should make PLplot nearly as powerful
> on Cygwin as it currently is on Linux, and I am very much looking forward to
> achieving that goal!

Yes, Cygwin is turning out to be a most enjoyable platform.

>
> N.B. although installing the above packages and running another noninteractive
> comprehensive test should be straightforward, I am well aware that I currently have
> another outstanding request for you concerning creating the "git format-patch"
> version of the current state of your new Fortran binding. Furthermore, I still have a lot
> of simple topics of my own I would like to finish up for the current release cycle.
> Therefore, these two requests from me to you should both be classified as
> "whenever convenient for you".
>
Well, getting to terms with git seems to be the most mentally demanding task. It ought to be a good exercise though.

Regards,

Arjen

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.