[vvbandeira]

flow/util/genReport.py -sv writes the summary at the end of each CI run.
It printed one block per failing design, in name order.
Each block counted [ERROR] lines instead of regressed metrics, and each block repeated the QoR baseline URL.
On master build 1736, every design showed "Found 1 metrics failures", but the 12 designs had 25 regressed metrics between them.
The report also hid some results: [WARN] lines from the QoR check, the INCONCLUSIVE verdict, and passing designs with DRC violations under the limit, which printed without a design name.

The summary now starts with one row per design, sorted by severity:

Code	Meaning
STOP	the flow did not reach the last stage
ERR	the flow finished with an [ERROR] in a stage log
DRC	Calibre DRC failed
QOR	QoR regression; designs with more regressed metrics first
WARN	the design passes, but a note needs attention

Detail sections per category follow the table, then a "Needs attention" section.
The rules that make a design pass or fail did not change.
The output file names that Jenkins archives did not change.

Example from the build 1736 data (shortened):

============================================================
SUMMARY: 67 designs, 12 failing, 55 passing
  flow stopped 0 | flow error 0 | Calibre DRC 0 | QoR regression 12
  Most regressed: finish__timing__setup__tns (9), globalroute__timing__setup__tns (6), cts__timing__setup__tns (4)
  QoR baseline: https://dashboard.precisioninno.com/builds/35280
============================================================

QOR   sky130hd/chameleon/base                          5 metrics: detailedroute__antenna__violating__nets, ...
QOR   ihp-sg13g2/gcd/base                              3 metrics: cts__timing__setup__tns, ...
...
WARN  asap7/aes-block_aes_rcon/base                    missing metadata-generate.log, metadata-check.log

------------------------------------------------------------
QOR REGRESSION (12)
------------------------------------------------------------
ihp-sg13g2/gcd/base: 3 metrics over the limit
    metric                           current       base          limit
    cts__timing__setup__tns          -5.87544      -4.45276      -5.343312
    finish__timing__setup__tns       -5.66599      -3.87928      -4.655136
    globalroute__timing__setup__tns  -7.59107      -6.19756      -7.437072

Other changes:

• Each error line shows the log file it came from, and repeated errors print once with a count.
• A stopped flow with no [ERROR] line shows the end of its last log, correctly indented, and names a kill signal when it finds one.
• The "Failed to open ..." lines before the banner are replaced by a "missing ..." note on the design.
• Designs are named platform/design/variant, the same identity that the QoR check uses.
• The per-design mode (no -s) creates the reports directory when a flow stopped before it existed.

[gemini-code-assist]

Code Review

This pull request refactors the report generation utility genReport.py and its test suite test_genReport.py. The changes introduce structured log parsing, improved error and warning classification, support for multiple verbosity levels, and robust handling of non-UTF-8 log files. The test suite has been updated and expanded to cover these new reporting features and edge cases. There are no review comments, so I have no feedback to provide.

[openroad-ci]

🔍 QoR check

Metrics reflect the PR merge build — i.e. what will land on the target branch.

Commit 5fc5977 · Jenkins build #1 · Baseline: build · View build on dashboard

62 design(s) checked — 0 with regression(s), 0 without a comparable baseline.