-
Notifications
You must be signed in to change notification settings - Fork 380
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
Add facility to package failed runs #424
Comments
I'll be honest, I have no idea what on earth is going on here: https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/b549b82ff7a3c004a0117ebea2ef970f2d4c7207/flow/util/utils.mk#L57 The (unofficial) ruby script I made simply tries to extract the variables and files, then replace them with resolved values. Does this do something similar? |
It produces a tgz with runme script that (1) sources a script that captures all the envars set by make and (2) invokes openroad on the proper tcl file to reproduce the step that is failing. That tgz is a complete capture of the problem and is trivial for a developer to unpack and run. |
Huh. I like the idea of the runner script being the one to set the environment variables. I'll look into it. |
* or_issue.py (RE: #424) * Reflect changes based on @maliberty's review * 66 -> os.EX_NOINPUT
Closed in #428. |
* or_issue.py (RE: The-OpenROAD-Project#424) * Reflect changes based on @maliberty's review * 66 -> os.EX_NOINPUT
* or_issue.py (RE: #424) * Reflect changes based on @maliberty's review * 66 -> os.EX_NOINPUT
In OpenROAD-flow-scripts the 'make issue' facility makes it easy to package up all necessary files to reproduce a problem in order to reproduce an issue. OpenLane needs a similar capability. See the on-going discussion in The-OpenROAD-Project/OpenROAD#703.
The text was updated successfully, but these errors were encountered: