-
Notifications
You must be signed in to change notification settings - Fork 72
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
TypeError
exception when running simulation
#255
Comments
same err: ----------------------------------------------------------------------------- live log call ------------------------------------------------------------------------------ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― test_dff_verilog ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
test_dff.py:11: /usr/lib/python3.11/asyncio/runners.py:190: in run filename = None
:812: TypeError test_dff.py::test_dff_verilog ⨯ 50% █████ Results (0.33s): |
Would be great if you could provide PR for this. |
When trying to run a simulation, a
TypeError
exception is being thrown; error shown below. I was finally able to track down the error tolibpython3.12.so
not being installed, but it would be nice if cocotb-test would be able to detect this case and provide a more informative error. I believe that cocotb-test could check iffind_libpython.find_libpython()
returnedNone
or an empty string and raised an error at simulator.py:207 instead of settingLIBPYTHON_LOC
to an empty string value which results in theTypeError
getting thrown fromsubprocess.py
.cocotb version - 1.8, stable
cocotb-test version - 0.2.5 (installed w/ pip)
operating system - Ubuntu, 20.06.6 LTS, 64-bit
simulator version - GHDL, 4.0.0
python version - 3.12, in a virtual environment
error -
The text was updated successfully, but these errors were encountered: