I pushed things to `next` for UFL and FFC last night which could possibly have an effect, but that unit test runs fine on my machine with `next`, including this changeset which was the latest when I pulled:
commit b3a05caf8e0924e300065570bf3cb8f3d85172e4 Merge: a16a895 21a6fc7 Author: Garth N. Wells <[email protected]> Date: Tue Jun 3 20:16:27 2014 +0100 Merge branch 'garth/fix-issue-285' into next -- Anders On Wed, Jun 04, 2014 at 09:24:48AM +0100, Garth N. Wells wrote: > I got the error on my machine too. My suspicion was the order in > which 'next' for the different components is updated on the > buildbots. > > Garth > > > On Wed, 4 Jun, 2014 at 9:22 AM, Martin Sandve Alnæs > <[email protected]> wrote: > >How do they affect the parameters? Where do I look? > > > >Martin > > > > > >On 4 June 2014 10:18, Anders Logg <[email protected]> wrote: > >>On Wed, Jun 04, 2014 at 09:32:24AM +0200, Martin Sandve Alnæs wrote: > >>> The next buildbot fails with a compile error in bench because > >>of some changes > >>> to Assembler last night. > >>> > >>> Before that it failed because of > >>> > >>> > >>> ERROR: test_nasty_jit_caching_bug (__main__.JIT) > >>> ---------------------------------------------------------------------- > >>> Traceback (most recent call last): > >>> File "./test.py", line 36, in test_nasty_jit_caching_bug > >>> parameters["form_compiler"]["representation"] = representation > >>> File > >>> "/home/buildbot/fenicsbbot/next/dolfin-full/lib/python2.7/site-packages/ > >>> dolfin/cpp/common.py", line 2087, in __getitem__ > >>> raise KeyError, "'%s'"%key > >>> KeyError: "'form_compiler'" > >>> > >>> > >>> and then a segfault. I don't think those are mine? > >> > >>Your changesets seem to be the only ones that affect parameters > >>in the > >>Python layer, so it's likely you... > >> > > > _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
