Kaleb Barrett
Kaleb Barrett
> So are you saying that: > > * `.value` should use `vpiInertialValue` and not go through `Scheduler._write_calls` > * `setimmediatevalue` should use `vpiNoDelay` The 1st I'm still iffy on....
@toddstrader that sounds good to me.
I feel like closing was a mistake. AFAIK there is no documentation on how to collect or view code coverage in either the CONTRIBUTING.md or the ReadTheDocs documentation.
So you were talking about HDL code coverage, not Python code coverage? If so we don't have documentation on that yet. We should point to those extensions at a minimum.
> Look like Questas handles are not updated just after the cancelation of a task. Could you explain what you mean here? Certainly the stacktrace is unexpected.
@Febbe that's been a point of contention for a while and also an interface breaking change. I suggested we instead replace `First` and `Combine` in #2659. But regardless of that,...
I wonder if this is more of the same as #3010. There are notes all over the VPI about "Modelsim doesn't like this so we do something awful lol". The...
Questa version is 2019.10 per the error message. It might be worth seeing if a newer version of the simulator prevents the stacktrace, otherwise at some point someone will go...
Strange it isn't covering the new line, cocotb_build_libs.py says the define is VERILATOR?
@marlonjames Do we trust to merge this as is, or should we wait until Verilator CI changes are backported?