-
Notifications
You must be signed in to change notification settings - Fork 250
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
Get run CLI args from Results #579
Comments
The args should be readable from the VUnit object already. No need to wait to post_run. |
I tried to get it from VUnit, but I didn't succeed. I assume I need to execute Lines 751 to 764 in 895e8c4
Lines 921 to 942 in 895e8c4
Lines 78 to 115 in 895e8c4
Lines 139 to 160 in 895e8c4
Lines 187 to 224 in 895e8c4
Lines 170 to 188 in 895e8c4
Lines 227 to 260 in 895e8c4
Lines 264 to 278 in 895e8c4
Line 226 in 895e8c4
|
Oh are you talking about the argv to ghdl? I thought you were talking about the run. py argv. I am not sure we want to expose the GHDL command on the public API. I am not sure we can even promise that it will always be one command even for all simulators. |
Yes. The point is that
I think it'd be good to retrieve the sequence of commands that VUnit uses for simulation and the arguments for compilation in a machine-readable format (i.e. not parsing the logs). I'm ok with not adding them to the public API, but to provide guidelines about how to achieve it. Would you be open to merging something like Lines 260 to 267 in effda9b
|
If we add a public abstraction of the simulator it must not constrain the implementation of any current or future simulator. Do we want to promise that each simulator will always need one command to run a test? It seems like yor use case is quite niche and GHDL specific and would be better accommodated by something similar as an args.txt you propose. Maybe make it have some standard format such as json such that string escaping and tokenization does not become a problem. |
The main motivation to propose exposing it with a mechanism different from
I'll convert it to JSON and I'll propose a PR. |
Merged as part of #606. |
It would be useful if the CLI args that are used to run each test/config were available programmatically (either in
post_run
or through--export-json
). Something similar to:In https://github.com/VUnit/vunit/pull/568/files#diff-d11203cc5c5e59bf50c8fe619e03e39d, I'm using a modified ghdl_interface to write the args to a txt file, as a workaround.
This would allow to indirectly retrieve the version of the standard, as commented in #577 (comment).
The text was updated successfully, but these errors were encountered: