dolfin team mailing list archive

[Johan Hake <hake.dev@xxxxxxxxx>]

I think the base class approach would work. Change RuntimeError, to
StandardError.

The catching is done within UnitCase.assertRaises. Not sure one can pass
several Error types to that method.

Johan

On 02/14/2013 11:28 AM, Martin Sandve Alnæs wrote:
> They probably have a shared baseclass, or you can catch both in one except.
> 
> Martin
> 
> Den 14. feb. 2013 11:16 skrev "Johan Hake" <hake.dev@xxxxxxxxx
> <mailto:hake.dev@xxxxxxxxx>> følgende:
> 
>     It looks like NumPy has changed the type of error raised when trying to
>     write to a none-writable array. With numpy version 1.6.2 I get a
>     RuntimeError. It looks like the error in the build bot is a ValueError:
> 
>     from numpy import *
>     a = zeros(2)
>     a.flags.writeable = False
>     a[0] = 1
> 
>     Maybe we should have something like:
> 
>     if np.__version__ <= 1.6.2:
>       error_type = RuntimeError
>     else:
>       error_type = ValueError
> 
> 
>     ?
> 
>     J
> 
>     On 02/14/2013 10:24 AM, Johannes Ring wrote:
>     > I added a new slave to the buildbot yesterday, running the development
>     > branch of the upcoming Ubuntu 13.04. It fails to run several of the
>     > unit tests with error messages like the one below. Any idea what the
>     > problem could be?
>     >
>     > Johannes
>     >
>     > ERROR: test_cell_iterators (__main__.MeshIterator)
>     > Iterate over cells
>     > ----------------------------------------------------------------------
>     > Traceback (most recent call last):
>     >   File "./MeshIterator.py", line 122, in test_cell_iterators
>     >     self.assertRaises(RuntimeError, assign, con, i)
>     >   File "/usr/lib/python2.7/unittest/case.py", line 476, in
>     assertRaises
>     >     callableObj(*args, **kwargs)
>     >   File "./MeshIterator.py", line 121, in assign
>     >     con(i)[0] = 1
>     > ValueError: assignment destination is read-only
>     >
>     >
>     >
>     > On Thu, Feb 14, 2013 at 7:56 AM,  <buildbot@xxxxxxxxxxxxxxxxx
>     <mailto:buildbot@xxxxxxxxxxxxxxxxx>> wrote:
>     >> The Buildbot has detected a new failure on builder
>     dolfin-1.1.x-full-raring-amd64 while building FEniCS Project.
>     >> Full details are available at:
>     >>
>      http://fenicsproject.org:8010/builders/dolfin-1.1.x-full-raring-amd64/builds/1
>     >>
>     >> Buildbot URL: http://fenicsproject.org:8010/
>     >>
>     >> Buildslave for this Build: raring-amd64
>     >>
>     >> Build Reason: The Nightly scheduler named
>     'nightly-dolfin-1.1.x-full' triggered this build
>     >> Build Source Stamp: [branch 1.1.x] HEAD
>     >> Blamelist:
>     >>
>     >> BUILD FAILED: failed make run_unittests
>     >>
>     >> sincerely,
>     >>  -The Buildbot
>     >>
>     >>
>     >>
>     >>
>     >> --
>     >> Mailing list: https://launchpad.net/~fenics-buildbot
>     >> Post to     : fenics-buildbot@xxxxxxxxxxxxxxxxxxx
>     <mailto:fenics-buildbot@xxxxxxxxxxxxxxxxxxx>
>     >> Unsubscribe : https://launchpad.net/~fenics-buildbot
>     >> More help   : https://help.launchpad.net/ListHelp
>     >
>     > _______________________________________________
>     > Mailing list: https://launchpad.net/~dolfin
>     > Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
>     <mailto:dolfin@xxxxxxxxxxxxxxxxxxx>
>     > Unsubscribe : https://launchpad.net/~dolfin
>     > More help   : https://help.launchpad.net/ListHelp
>     >
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~dolfin
>     Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
>     <mailto:dolfin@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~dolfin
>     More help   : https://help.launchpad.net/ListHelp
>