test_torus failing on run

[epsilon-0]

I've been trying to update MeshPY to latest on Gentoo and am running the tests to check if the package is installed correctly.

It fails with the following log

 * python3_7: running distutils-r1_run_phase python_test
===================================================================== test session starts ======================================================================
platform linux -- Python 3.7.9, pytest-6.0.2, py-1.9.0, pluggy-0.13.1 -- /usr/bin/python3.7
cachedir: .pytest_cache
rootdir: /var/tmp/portage/dev-python/meshpy-2018.2.1_p1/work/meshpy-6f4f9418f5f02b414d561bd8de710c4f1349ea72
plugins: flaky-3.7.0
collecting ... collected 5 items

test/test_meshpy.py::test_triangle_refine PASSED                                                                                                         [ 20%]
test/test_meshpy.py::test_point_attributes PASSED                                                                                                        [ 40%]
test/test_meshpy.py::test_tetgen PASSED                                                                                                                  [ 60%]
test/test_meshpy.py::test_torus Fatal Python error: Aborted

Current thread 0x00007f04dd287740 (most recent call first):
  File "/var/tmp/portage/dev-python/meshpy-2018.2.1_p1/work/meshpy-6f4f9418f5f02b414d561bd8de710c4f1349ea72-python3_7/lib/meshpy/tet.py", line 162 in tetrahedralize
  File "/var/tmp/portage/dev-python/meshpy-2018.2.1_p1/work/meshpy-6f4f9418f5f02b414d561bd8de710c4f1349ea72-python3_7/lib/meshpy/tet.py", line 190 in build
  File "/var/tmp/portage/dev-python/meshpy-2018.2.1_p1/work/meshpy-6f4f9418f5f02b414d561bd8de710c4f1349ea72/test/test_meshpy.py", line 150 in test_torus
  File "/usr/lib/python3.7/site-packages/_pytest/python.py", line 180 in pytest_pyfunc_call
  File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.7/site-packages/_pytest/python.py", line 1570 in runtest
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 153 in pytest_runtest_call
  File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 247 in <lambda>
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 294 in from_call
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 247 in call_runtest_hook
  File "/usr/lib/python3.7/site-packages/flaky/flaky_pytest_plugin.py", line 138 in call_and_report
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 117 in runtestprotocol
  File "/usr/lib/python3.7/site-packages/_pytest/runner.py", line 100 in pytest_runtest_protocol
  File "/usr/lib/python3.7/site-packages/flaky/flaky_pytest_plugin.py", line 94 in pytest_runtest_protocol
  File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.7/site-packages/_pytest/main.py", line 321 in pytest_runtestloop
  File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.7/site-packages/_pytest/main.py", line 296 in _main
  File "/usr/lib/python3.7/site-packages/_pytest/main.py", line 240 in wrap_session
  File "/usr/lib/python3.7/site-packages/_pytest/main.py", line 289 in pytest_cmdline_main
  File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.7/site-packages/_pytest/config/__init__.py", line 158 in main
  File "/usr/lib/python3.7/site-packages/_pytest/config/__init__.py", line 180 in console_main
  File "/usr/lib/python-exec/python3.7/pytest", line 11 in <module>
/var/tmp/portage/dev-python/meshpy-2018.2.1_p1/temp/environment: line 2908:  3117 Aborted                 pytest -vv

Please let me know what else I should give out to get this working!

[inducer]

Thanks for the report. Unfortunately, I'm not able to reproduce your issue. In fact, the meshpy tests pass for me in multiple environments, including Python 3.7 on Github's CI:

https://github.com/inducer/meshpy/runs/1033389699

as well as CI in my own (Debian Linux) environment:

https://gitlab.tiker.net/inducer/meshpy/-/jobs/167592

As such, perhaps the most important thing you can would be to enable me to reproduce the issue (and also produce a backtrace). In addition, if the issue occurs inside of tetgen, then it might be worthwhile to reproduce it with command-line tetgen and report it upstream.

[mwtoews]

This might be a coincidence, but there is a downstream issue conda-forge/meshpy-feedstock#23 with the same test_torus that fails on aarch64 linux (aka arm64). However, the possible difference is that it gets "stuck" in an infinite loop of TetGen 1.5 here.

[rfiorella]

@mwtoews @inducer it looks like the control structure for locate() in TetGen 1.6 is different in a way that seems less prone to getting stuck in an infinite loop, so it's plausible that solving #89 will also solve this issue.

I can try to work on #89, if there haven't been other efforts toward resolving this

[inducer]

I'm not aware of any existing efforts.