You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is my first time using cocotb-test and I'm using it with Verilator. I have used Verilator fairly extensively with just C++ testbenches. I'm following some alexforencich examples for cocotb-test which are basically this:
While this works fine for functional RTL, I found that if you have an RTL bug that the verilator linter would normally catch for you (like a misnamed variable), cocotb-test is suppressing the Verilator output that results from the "perl verilator ..." call, so all you get is the cryptic message: "SystemExit: Process .../verilator terminated with error 1". In reality the verilator command that failed prints a ton of useful debugging information before returning that value of 1, and it seems the cocotb-test should be displaying it.
The text was updated successfully, but these errors were encountered:
This is my first time using cocotb-test and I'm using it with Verilator. I have used Verilator fairly extensively with just C++ testbenches. I'm following some alexforencich examples for cocotb-test which are basically this:
cocotb_unit_test.py:
syncfifo_test.py:
A makefile invokes the pytest file like this:
While this works fine for functional RTL, I found that if you have an RTL bug that the verilator linter would normally catch for you (like a misnamed variable), cocotb-test is suppressing the Verilator output that results from the "perl verilator ..." call, so all you get is the cryptic message: "SystemExit: Process .../verilator terminated with error 1". In reality the verilator command that failed prints a ton of useful debugging information before returning that value of 1, and it seems the cocotb-test should be displaying it.
The text was updated successfully, but these errors were encountered: