On 2016-11-30 07:54- Arjen Markus wrote:
> Yes, [dashboard submission] turned out to be easier than I thought.
My first run failed because I had forgotten to adjust the path before
running ctest -D Experimental. (I was misled by the term "dashboard"
which seems to have several different meanin
Hi Alan,
I will try this new approach rightaway. This is an obscure bug indeed.
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> This is a most interesting result that puzzled me for a long while until I
> believe I
> have now found the solution.
>
>
Hi Alan,
By the looks of the first part of the output it has done the trick indeed :).
No compiler errors or warnings according to ctest.
Regards,
Arjen
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> This is a most interesting result that puzzle
On 2016-11-30 13:57- Arjen Markus wrote:
> By the looks of the first part of the output it has done the trick
indeed :). No compiler errors or warnings according to ctest.
Hi Arjen:
I was very happy to see your clean dashboard (aside from some spurious
warning counts for the configuration st
On 11/27/2016 01:40 PM, Alan W. Irwin wrote:
> It is good to hear it is likely going to be even easier than I thought. I
> guess that -py3 flag is needed for more complex Python bindings than ours.
Spoke too soon I guess. It appears that swig detects which version of
Python you are using and c