提交 9b6ca667 authored 作者: Olivier Delalleau's avatar Olivier Delalleau

Extended known failure case to numpy 1.6.x instead of only 1.6.0, until we know…

Extended known failure case to numpy 1.6.x instead of only 1.6.0, until we know better about the intended numpy behavior
上级 d83b9045
...@@ -4741,17 +4741,17 @@ class test_arithmetic_cast(unittest.TestCase): ...@@ -4741,17 +4741,17 @@ class test_arithmetic_cast(unittest.TestCase):
a_type == 'complex128' and a_type == 'complex128' and
b_type == 'float32' and b_type == 'float32' and
combo == ('scalar', 'array') and combo == ('scalar', 'array') and
numpy.__version__ == '1.6.0' and numpy.__version__.startswith('1.6.') and
theano_dtype == 'complex128' and theano_dtype == 'complex128' and
numpy_dtypes == ['complex64', numpy_dtypes == ['complex64',
'complex64']): 'complex64']):
# In numpy 1.6.0 adding a complex128 with # In numpy 1.6.x adding a complex128 with
# a float32 may result in a complex64. This # a float32 may result in a complex64. This
# may be a bug (investigation is currently # may be a bug (investigation is currently
# in progress), so in the meantime we just # in progress), so in the meantime we just
# mark this test as a known failure. # mark this test as a known failure.
raise KnownFailureTest('Known issue with ' raise KnownFailureTest('Known issue with '
'numpy 1.6.0, see #761') 'numpy 1.6.x, see #761')
# In any other situation: something wrong is # In any other situation: something wrong is
# going on! # going on!
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论