pytest: Occasional AST constructor depth mismatch
- a detailed description of the bug or problem you are having
In some of our CI runs in the ibis project we occasionally see failures around AST depths mismmatching.
It’s hard for me to reproduce locally.
- ~output of
pip listfrom the virtual environment you are using~
The number of transitive dependencies for ibis is large. I’m happy to list them here, but it may require a bit of discussion/help to get someone setup to reproduce this
- pytest and operating system versions
pytest: 7.2.2 os: linux 6.1.2 (NixOS)
- ~[ ] minimal example if possible~
I don’t know exactly what is minimal here, I’m having trouble reproducing it locally.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 3
- Comments: 16 (16 by maintainers)
Commits related to this issue
- 💚 CI: Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x - More information: https://github.com/pytest-dev/pytest/issues/10874 — committed to abhiTronix/vidgear by abhiTronix a year ago
- 💚 CI: Made temporary fix platform independent. - Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: https://github.com/pytest-dev/pytest/issues/10874 — committed to abhiTronix/vidgear by abhiTronix a year ago
- 💚 CI: Extended fix to more tests. - Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: https://github.com/pytest-dev/pytest/issues/10874 — committed to abhiTronix/vidgear by abhiTronix a year ago
- 💚 CI: Extended fix to more Webgear_RTC tests. - Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: https://github.com/pytest-dev/pytest/issues/10874 — committed to abhiTronix/vidgear by abhiTronix a year ago
- 💚 CI: Extended fix to all Webgear_RTC tests. - Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: https://github.com/pytest-dev/pytest/issues/10874 — committed to abhiTronix/vidgear by abhiTronix a year ago
- 🏗️ Maintenance: Replaced python `3.7.x` support with `3.11.x` legacy (Fixed #369) [#370] 🚧 Setup.py: - Removed support for python-3.7 legacies - 📌 Raised `python_requires` to `>=3.8`. Thereby... — committed to abhiTronix/vidgear by abhiTronix a year ago
- 🎉 Released VidGear Stable `v0.3.2` [#379] ### New Features ✨ - **NetGear:** * Added new `kill` parameter to `close()` method to forcefully kill ZMQ context instead of graceful exit only in th... — committed to abhiTronix/vidgear by abhiTronix 10 months ago
No worries, I understand!
One thing I can think of to reproduce the problem is to use a pytest fork which uses a try/except block around the
ast.parsecall:When that raises a
SystemError, dumpcontentto a file. Hopefully then you can use that content to create a smaller reproducer.