Lots of warnings about PDKs in build process. Since non-actionable, can they be suppressed ?

[hzeller]

During the build, about 44000 (yes, 44 thousand) lines with warnings are emitted, that point to benign or at least non-actionable situations while parsing the PDKs, such as skywater or asap7.

These obstruct the view of actual potential build issues and warnings. Given that these are probably benign, and currently entirely non-actionable (and the build process should focus on only emitting things that can be addressed), could they be suppressed in the corresponding build rules ? Looks like all the warnings have number-identifiers, so I suspect there might be a way to suppress a set of warnings just by these numbers.

Here a breakdown:

bazel build --noshow_loading_progress --noshow_progress -c opt ... -k > /tmp/buildlog.txt 2>&1
awk '/^\[WARNING/ {print $2}' /tmp/buildlog.txt | sort | uniq -c | sort -n
      3 RSZ-0062]
      6 DRT-0240]
      6 IFP-0028]
      6 PDN-1024]
     12 DRT-0145]
     24 FIN-0010]
     33 ODB-0220]
     42 ORD-0046]
     96 STA-1140]
    155 DRT-0422]
    360 STA-1265]
    450 STA-1212]
    765 STA-1173]
  42042 STA-1256]

If there are actual issues in the PDK and the way the are parsed, this should be addressed separately, fixed one-by-one and then re-enable the corresponding warning once fully resolved. But right now, it just drowns the output in a wall of text.

[ericastor]

I think most of these are arguably issues upstream in https://github.com/hdl/bazel_rules_hdl, or (as you say) in the upstream PDKs.

Either way, I'll reach out to the maintainers for the rules to start.

[ericastor]

Update: I have a PR out to start the discussion, at hdl/bazel_rules_hdl#417.

Once that (or something similar) lands, we can start suppressing warnings in our own targets.