Eric Wieser

Does this happen every time? If you, can you check if `master` suffers the same problem?

Test in question is: https://github.com/pygae/clifford/blob/2da66d3243651a3fe50363158c2b6cdc9dc1d725/clifford/test/test_cga.py#L84-L92

Can you run with python fault handling enabled so that we get a traceback?

It looks like its supposed to be enabled by default... https://docs.pytest.org/en/stable/usage.html#fault-handler

Using `python3 -X faulthandler -m pytest` instead of `pytest` might force it to jump into action

Can you diagnose which line is failing by inserting print statements between each line of the test?

Thanks, that gives me plenty to work with. I wonder whether this is actually a numpy incompatibility.

I imagine this means that this reproduces on windows

And my guess would be that the bug was fixed in clifford by a1b1ba3519612af4d0e0c842ff290ee0f5d25ca1

Either way, thanks for the dive into the cause - I've reported a bug against numpy, which I might take a look at next time I put on my numpy...