The-Compiler
commented
4 years ago Not much we can do without having a way to reproduce this... However, something that might help to find the issue (whether that's in pytest or in your DLL) is a git bisect. This tells us which commit in pytest exactly introduces the issue, by letting git always test the middle between two commits.
To do so, run something like this (untested):
git clone https://github.com/pytest-dev/pytest.gitC:\my\private\path\privatevenv\Scripts\pip install -e pytestcd pytest
Now for the following commands, use two different terminals, one where you do the bisect in the pytest repository, and one where you run pytest in your project directory:
git checkout 4.6.11- Verify that you can run
pytest test.pyin your project directory and that the issue does not occur (also check if the header showspytest-4.6.11like expected) git checkout 5.0.0- Verify that the issue does occur (and double check the header)
git bisect startgit bisect good 4.6.11git bisect bad 5.0.0
Then, git will check out the middle between the two. Test it, and do git bisect good or git bisect bad. If something is broken for unrelated reasons, do git bisect skip. After testing ~10 times, git should present you with the broken commit.
ghost
RonnyPfannschmidt
fossum
W2Q3Q1
Marco-Sulla
A detailed description of the bug or suggestion:
So, I used to run tests on windows 10 using pytest 3.x.x and custom plugins but I recently upgraded to pytest 5.x.x. Since then, each time I run a test featuring a call to a DLL using pythonnet 2.5.1, I get a generic windows access violation error. Even though I found similar cases online, each time accepted fix seemed to be to downgrade pytest - which I do not want to do, as I rather like the new functionalities.
Issue was reproduced with every pytest version above 5.0.0, including 6.0.0+. Versions under 4.6.11 did not allow me to reproduce the error.
Output of
pip listfrom the virtual environment you are using:my privatevenv pip list: Package Version
atomicwrites 1.4.0 attrs 19.3.0 colorama 0.4.3 comtypes 1.1.7 importlib-metadata 1.7.0 iniconfig 1.0.1 more-itertools 8.4.0 packaging 20.4 pip 19.0.3 pluggy 0.13.1 py 1.9.0 pycparser 2.20 pyparsing 2.4.7 pytest 5.4.3 pythonnet 2.5.1 pywin32 228 pywinauto 0.6.8 setuptools 40.8.0 six 1.15.0 toml 0.10.1 wcwidth 0.2.5 zipp 3.1.0
pytest and operating system versions:
platform win10 x64 -- Python 3.7.4 32 bits, pytest-5.3.4, py-1.9.0, pluggy-0.13.1
Minimal example if possible:
here is my code for test.py:
and the output I get when executing "pytest test.py":
As an additional question, is there a better way or methodology to troubleshoot this one ?
Thanks.