Remove dangling files, update parsing scripts across generators and workflows

[chetanyagoyal]

This PR attempts to remove hanging files (like ./openfasoc/generators/temp-sense-gen/tools/verify_op.sh) and includes their functionalities in the corresponding report parse files
Also does the same for the parse_rpt.py file found in the .github/scripts section to account for this functionality in the CI

[chetanyagoyal]

@saicharan0112 @msaligane

[chetanyagoyal]

@saicharan0112 As the ldo-gen tools folder does not have a parse report file, would you suggest that I make one along the lines of what the .github/scripts parse_rpt.py file does?

[saicharan0112]

@saicharan0112 As the ldo-gen tools folder does not have a parse report file, would you suggest that I make one along the lines of what the .github/scripts parse_rpt.py file does?

I think its a good idea to have all generators follow the same format to check for drc and lvs errors. tbh I would expect a function inside the main script itself but for now it is ok to have a different file.

Here is a suggestion.. can you list all files that are generated by the three generators (cryo-gen, ldo-gen and temp-sense-gen) and see if the existence of these files are checked along with the drc and lvs errors please?

[chetanyagoyal]

@saicharan0112 are there any other changes required before this is merged?

[saicharan0112]

There is a lot of code redundancy. I think you can have one single function for these checks (probably you can use the common directory outside the generators?) and reuse with generator specific files to do checks.

[saicharan0112]

Hope you are working on logic summary in the beginning of parse_rpt.py under .github/scripts and common/check_gen_files.py

[chetanyagoyal]

Hope you are working on logic summary in the beginning of parse_rpt.py under .github/scripts and common/check_gen_files.py

Addressed all issues, please check

[saicharan0112]

Thanks @chetanyagoyal . It can still be improved but it looks very good for now. Right now cryo-gen and ldo are not reaching till the stage where the reports are checked and the outputs are verified, so let's see how it goes once they are active.