Skip to content
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 checks to tapeout flow ensure each job did not have execution errors #531

Open
jeffdi opened this issue Feb 28, 2024 · 1 comment
Open
Assignees

Comments

@jeffdi
Copy link
Collaborator

jeffdi commented Feb 28, 2024

Any error in any step needs to stop the process (precheck or tapeout) and report back the error.

I disagree with the above statement. I think tapeout should complete every check so it can identify all errors in each round of verification, and then all can be fixed before the next round of verification. What I think this ticket should cover are cases where the check failed due to an error in executed.

An example: a shuttle oasis file had multiple top level cells. One of the metal DRC jobs failed because of that. Multiple error messages was put in the log file and a blank RDB file was output. The summary script then listed zero errors in the summary file. This made it through onto the tapeout server without being identified as a problem.

mpw_precheck and tapeout both need to not only check the xml output for errors, but also check for error and warning messages in the log file.

@jeffdi
Copy link
Collaborator Author

jeffdi commented Feb 28, 2024

does an error with any of the steps stop the flow and generate an error?

@DavidRLindley DavidRLindley changed the title add checks to tapeout flow ensure each of the steps has completed successfully Add checks to tapeout flow ensure each job did not have execution errors Dec 5, 2024
@DavidRLindley DavidRLindley assigned a-omla and unassigned jeffdi Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants