vaughnbetz

Updating the branch so CI is going to kick off again ....

Both strong and nightly failures are a few large QoR changes on small designs (some better, some worse): OK to just update the golden results for them.

Can update the few numbers by hand, or use https://docs.verilogtorouting.org/en/latest/README.developers/?highlight=golden#generating-new-qor-golden-result

CI is green and the code looks OK to me -- should this be merged at this point? @aman26kbm @sdamghan please let me know.

document build failure is infrastructure issue so can remove draft. Are all free/malloc/calloc/realloc gone from related libraries like libarchfpga? Can you test runtime with QoR run on titan or vtr...

All looks good except placed_wirelength_est looks too good (predicting a 6% reduction in wirelength, which shouldn't happen). Is that one a typo?

Looked at the results some more. Everything looks good except placed_wirelength_est looks too good in both comparisons. Was there a change in the master code? Is there a bug introduced...

Documentation failure is an infrastructure issue; ignore it.

Not sure about the -1 place_wirelength_est in the github artifacts; maybe not parsed out in the CI tests? The regression and CI scripts and conf files are fairly involved and...

Thanks @hzeller . Good suggestions. @jmah76 : if placed_wirelength_est is -1 in the master and your code, then it is fine. If it is -1 in your code but not...