On Mon, Jan 16, 2017 at 10:27:19PM -0800, Adam Williamson wrote:

On Tue, 2017-01-17 at 05:33 +0000, Zbigniew Jędrzejewski-Szmek wrote:

...

On Tue, Jan 17, 2017 at 05:29:35AM +0000, Zbigniew Jędrzejewski-Szmek wrote:

...

On Wed, Jan 11, 2017 at 04:28:18AM +0000, Zbigniew Jędrzejewski-Szmek wrote:

...

...

python3-sympy-0:1.0-3.fc25.noarch

Pfff, it still fails in the test suite :(

I'm chipping away at this one. There are some failing python2 tests which I had to disable, but it seems that things are mostly with python2. But it seems that the python3 code is plain broken (bad non-absolute imports).

Oh, Jerry beat me to it by taking a different route and disabling most test. That should work too, but I think it hides real problems with the python3 code...

Yeah. Please don't just disable tests. Tests exist for a reason.

We need to disable *some* tests, at least if we hope to build this quickly. It's just a question whether to disable more or less of them.

Most tests fail because of sympy/pyglet/xvfb/opengl interaction (#904851), not from sympy error per se — the same tests run fine on a "real" display.

Zbyszek