Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_torus failing on run #53

Open
epsilon-0 opened this issue Sep 26, 2020 · 1 comment
Open

test_torus failing on run #53

epsilon-0 opened this issue Sep 26, 2020 · 1 comment

Comments

@epsilon-0
Copy link

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
Copy link
Owner

inducer commented Sep 26, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants