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
Hi,
I think I encountered a bug in this wonderful plugin:
My setup:
In my company we use multiple Modelsim versions (Free Intel Starter Edition and regular full version, somewhat depending on use case)
In my run.py I have a number of custom command line arguments defined to influence the behavior of my simulation, so stuff that happens before simulation starts, like scanning huge directories, condensing that information to something that can be easily read on consecutive runs (speeding up simulation runs), setting some environment variables (i.e. setting what version to use) etc. which works quite well, when calling it from command line interface.
Using the VUnit Test Explorer I was expecting that vunit.options are always applied including "reload tests" and initial scan, but it seems they are only applied when pressing "Run *", so the whole preprocessing runs always with default values.
Is there a chance this might get fixed in the future?
Cheers,
Philipp
The text was updated successfully, but these errors were encountered:
Hi,
I think I encountered a bug in this wonderful plugin:
My setup:
In my company we use multiple Modelsim versions (Free Intel Starter Edition and regular full version, somewhat depending on use case)
In my run.py I have a number of custom command line arguments defined to influence the behavior of my simulation, so stuff that happens before simulation starts, like scanning huge directories, condensing that information to something that can be easily read on consecutive runs (speeding up simulation runs), setting some environment variables (i.e. setting what version to use) etc. which works quite well, when calling it from command line interface.
Using the VUnit Test Explorer I was expecting that vunit.options are always applied including "reload tests" and initial scan, but it seems they are only applied when pressing "Run *", so the whole preprocessing runs always with default values.
Is there a chance this might get fixed in the future?
Cheers,
Philipp
The text was updated successfully, but these errors were encountered: