Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[openbsd] test_fs_event.py causes Segmentation fault in python

Ouverte
#620 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
python

Piste de recherche

L’échec est signalé à la ligne 49 de tests/test_fs_event.py ; exécutez d’abord la commande pytest fournie avec PYTHONASYNCIODEBUG=1 sur OpenBSD. Examinez le défaut de segmentation de uvloop.loop pendant test_fs_event_change et vérifiez que le test ciblé se termine sans plantage une fois terminé.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

  • uvloop version: 0.20.0
  • Python version: 3.11.9
  • Platform: OpenBSD
  • Can you reproduce the bug with PYTHONASYNCIODEBUG in env?: Yes
  • Does uvloop behave differently from vanilla asyncio? How?:

Test output for the specific test

===>  Regression tests for py3-uvloop-0.20.0
cd /usr/ports/pobj/py-uvloop-0.20.0-python3/uvloop-0.20.0 && env PYTHONASYNCIODEBUG=1 py.test -vvv 'tests/test_fs_event.py::Test_UV_FS_EVENT_CHANGE::test_fs_event_change'
============================= test session starts ==============================
platform openbsd7 -- Python 3.11.9, pytest-8.2.0, pluggy-1.5.0 -- /usr/local/bin/python3.11
cachedir: .pytest_cache
rootdir: /usr/ports/pobj/py-uvloop-0.20.0-python3/uvloop-0.20.0
configfile: pyproject.toml
collecting ... collected 1 item

tests/test_fs_event.py::Test_UV_FS_EVENT_CHANGE::test_fs_event_change Fatal Python error: Segmentation fault

Current thread 0x0000063d21efb7d0 (most recent call first):
  File "/usr/ports/pobj/py-uvloop-0.20.0-python3/uvloop-0.20.0/tests/test_fs_event.py", line 49 in test_fs_event_change
  File "/usr/local/lib/python3.11/unittest/case.py", line 579 in _callTestMethod
  File "/usr/local/lib/python3.11/unittest/case.py", line 623 in run
  File "/usr/local/lib/python3.11/unittest/case.py", line 678 in __call__
  File "/usr/local/lib/python3.11/site-packages/_pytest/unittest.py", line 343 in runtest
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 173 in pytest_runtest_call
  File "/usr/local/lib/python3.11/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/local/lib/python3.11/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/local/lib/python3.11/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 241 in <lambda>
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 341 in from_call
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 240 in call_and_report
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 135 in runtestprotocol
  File "/usr/local/lib/python3.11/site-packages/_pytest/runner.py", line 116 in pytest_runtest_protocol
  File "/usr/local/lib/python3.11/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/local/lib/python3.11/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/local/lib/python3.11/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/local/lib/python3.11/site-packages/_pytest/main.py", line 364 in pytest_runtestloop
  File "/usr/local/lib/python3.11/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/local/lib/python3.11/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/local/lib/python3.11/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/local/lib/python3.11/site-packages/_pytest/main.py", line 339 in _main
  File "/usr/local/lib/python3.11/site-packages/_pytest/main.py", line 285 in wrap_session
  File "/usr/local/lib/python3.11/site-packages/_pytest/main.py", line 332 in pytest_cmdline_main
  File "/usr/local/lib/python3.11/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/local/lib/python3.11/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/local/lib/python3.11/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/local/lib/python3.11/site-packages/_pytest/config/__init__.py", line 178 in main
  File "/usr/local/lib/python3.11/site-packages/_pytest/config/__init__.py", line 206 in console_main
  File "/usr/local/bin/py.test", line 8 in <module>

Extension modules: uvloop.loop (total: 1)
Segmentation fault (core dumped)
*** Error 139 in . (Makefile:40 'do-test')
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3090 '/usr/ports/pobj/py-uvloop-0.20.0-python3/.test_done': @cd /usr/ports/devel/...)
*** Error 2 in /usr/ports/devel/py-uvloop (/usr/ports/infrastructure/mk/bsd.port.mk:2704 'test': @lock=py3-uvloop-0.20.0;  export _LOCKS_HEL...)
Langage dominant
Cython
Étoiles
11.9k
Forks
615
Métriques de merge des PR
Aucune PR mergée en 30 j

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de MagicStack/uvloop

Toutes les issues de MagicStack/uvloop

Issues similaires

Plus d'issues Operating Systems

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.