Kaleb Barrett
Kaleb Barrett
What is cocotb doing or not doing to break this that was changed upstream?
And if you think an upstream change broke this, why did you report the issue here?
Seems that the `hierarchicalName` in the design I tested that it's complaining about is `clk`. I don't see how that's wrong, or why the hierarchicalName *must* have a space in...
This was fixed upstream. Can you try it @jhladik?
At a minimum we should address all instances of `LOG_CRITICAL` used in functions called by cocotb.
From https://github.com/cocotb/cocotb/pull/1863#discussion_r429747349. Logging is not a great way to signal an error to either cocotb or the user via the log. For one, the error might be able to be...
`LOG_CRITICAL` is no more, as of #1793. The last usages in simulator-called code have been changed to usages of `gpi_sim_end` which calls `gpi_embed_event` to signal sim end to users.
We have a cocotb ecosystem compatibility test suite, but currently it only includes cocotb-coverage. https://github.com/cocotb/cocotb/actions/runs/9688874831/workflow I think adding pyuvm would be reasonable. But it's currently not in a state to...
"It" being the two working together. The ecosystem tests are there to ensure we aren't breaking things before a minor release is done. Since we are doing a major release,...
A test will need to be added to `.github/workflows/ecosystem-compat.yml`.