dolfin team mailing list archive

["Garth N. Wells" <gnw20@xxxxxxxxx>]

On 19/01/11 18:29, Anders Logg wrote:
> On Wed, Jan 19, 2011 at 10:26:35AM -0800, Johan Hake wrote:
>> On Wednesday January 19 2011 08:41:39 Anders Logg wrote:
>>> This seems to be related to the introduction of operator() in the C++
>>> interface.
>>>
>>> I'm suspecting that the problem is that one of the virtual eval
>>> functions has been moved up one level from Expression to
>>> GenericFunction. I'll try to fix it but Johan may spot to problem
>>> faster.
>>
>> Is this fixed now? I made an instant clean, or more precise, I errased all
>> dolfin_ in the cache.
> 
> I didn't think of running instant-clean. That was probably what fixed
> the problem.
> 
> Johannes, is instant-clean being run on the buildbots?
> 

It's not. It can be triggered by manually rebuilding instant on the
buildbot.

Garth

>> Everything runs smooth here. But I get a maximum recursion error while running
>> the function unit test:
> 
>> Traceback (most recent call last):
>>   File "test.py", line 90, in testOverLoadAndCallBack
>>     s0 = norm(interpolate(e0, V))
>>   File "/home/hake/local/lib/python2.6/site-
>> packages/dolfin/fem/interpolate.py", line 30, in interpolate
>>     Pv.interpolate(v)
>> RuntimeError: maximum recursion depth exceeded while calling a Python object
> 
> I will look into it.
> 
> --
> Anders
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp