dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #17300
Re: [Branch ~dolfin-core/dolfin/main] Rev 4406: has_gts -> has_cgal (fixes issue on Mac buildbot that doesn't have CGAL).
On Fri, Jan 29, 2010 at 12:36 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> On Fri, Jan 29, 2010 at 12:08:21PM +0100, Johannes Ring wrote:
>> [resending to include list]
>>
>> On Fri, Jan 29, 2010 at 11:29 AM, Anders Logg <logg@xxxxxxxxx> wrote:
>> > Are there still any HAS_CGAL issues to fix or has this been sorted
>> > out?
>>
>> I'm not sure but the C++ function demo fails on the Mac buildbot with
>> the following message:
>>
>> $ ./test
>> Solving linear variational problem
>> Matrix of size 4913 x 4913 has 126785 nonzero entries.
>> Solving linear system of size 4913 x 4913 (PETSc LU solver, umfpack).
>> ##Failure Location unknown## : Error
>> Test name: Eval::testArbitraryEval
>> uncaught exception of unknown type
>>
>> Failures !!!
>> Run: 1 Failure total: 1 Failures: 0 Errors: 1
>>
>> Could it be because CGAL is missing?
>
> I don't know. I saw some strange errors yesterday in testArbitraryEval
> which went away after I did instant-clean. Is that done on the
> buildbots before they run?
It is only done nightly when a rebuild of Instant is triggered.
However, one can force instant-clean to run by forcing a rebuild of
Instant. But I don't think that is the problem here since I just
logged into the Mac buildbot and ran instant-clean and then the
function test again and I got the same error.
>> > I vaguely remember that I promised to add some #ifdefs before
>> > Christmas but never got around to it.
>>
>> I think that was for LAPACK. Actually, the test program you made for
>> the LAPACK pkg-config generator did not work very well on the Windows
>> buildbot. It completely stalls at the call to dgels_. I never figured
>> it out so I had to turn off the Windows buildbot.
>
> Could we add some #ifdef WINDOWS around it?
I don't think that will be necessary because I tried your test program
now with a different LAPACK binary that I found and it ran just fine.
I guess there must be something wrong with my self-made LAPACK binary.
I will look into it.
Johannes
Follow ups
References