On 2019-04-11 10:54, Drew Parsons wrote:
On 2019-04-11 04:38, Paul Gevers wrote:
The score isn't great (and not all results are in): 3/14 failure (2 in
unstable, 1 in testing so far). Can you please have a look?
Apparently the same test failure does occur in python3 tests, but only
some of the time not all of the time. Weird.
I've uploaded 1.1.0-6 now to skip the same 2 tests in python3.
1.1.0-6 puts us in the clear with respect to the MemoryError failures.
10/10 test runs passed in unstable
9/10 test runs passed in testing.
The one failure is odd. It's not in the same class as previous test
failures, not a MemoryError.
It appears to be a true test failure, failing
_trustregion_constr.tests.test_canonical_constraint.test_concatenation
in
/usr/lib/python2.7/dist-packages/scipy/optimize/_trustregion_constr/tests/test_canonical_constraint.py:179
with
if np.any(f0[mask] < lb[mask]) or np.any(f0[mask] > ub[mask]):
raise ValueError("`x0` is infeasible with respect to some "
"inequality constraint with `keep_feasible`
"
"set to True.")
E ValueError: `x0` is infeasible with respect to some
inequality constraint with `keep_feasible` set to True.
This happens in the atlas tests (atlas provides lapack/blas), which is
not core scipy as such, since lapack can be provided by openblas.
This particular failure only happened once.
