Emergency Self-Construct

@eric-wieser sure, could you point me at some documentation on how to do that?

Yeah, I think this didn't really get us any further: ``` zsh» python3 -X faulthandler -m pytest clifford/test/test_cga.py::test_round_from_center_radius_init ========================================================================= test session starts ========================================================================= platform darwin -- Python 3.7.9, pytest-6.1.1, py-1.9.0,...

So, I have some news on this. It seems like `pytest` was capturing the stdout/stderr. Adding the `-s` flag for no-capture, results in the following. ``` zsh» pytest -s -v...

This is the debugging patch which is responsible for the output lines: ``` diff --git i/clifford/test/test_cga.py w/clifford/test/test_cga.py index 618e57ee0d..0fc5e6f8ac 100644 --- i/clifford/test/test_cga.py +++ w/clifford/test/test_cga.py @@ -83,13 +83,20 @@ def test_from_points_construction(cga,...

Looks like it might be the line ``` npt.assert_almost_equal(c.center_down, 3*e1+4*e2) ```

@eric-wieser that was a good hunch, I tried with Numpy 1.18.5 and the test did not segfault.

@eric-wieser shall we keep the issue open? I made the integration tests pass, for now: https://github.com/numba/numba-integration-testing/pull/56

@sklam, i just checked and the following config fails these tests too: ``` $ conda list | grep "numba\|clifford\|llvmlite" # packages in environment at /Users/esc/miniconda3/envs/clifford: clifford 1.4.0.dev0 pypi_0 pypi llvmlite...

@sklam is there anything that can be done to remedy this on the Numba side?

The documentation here https://llvm.org/docs/LangRef.html#terminator-instructions agrees that `br` is a terminator.