Errors hidden on default loglevel, but visible on verbose loglevels.

[c-93]

Describe the bug Increasing the verbosity setting shows errors, which are invisible on the default verbosity level.

Version 1.2.48

To Reproduce

• Manually modify verbosity to some higher value, e.g. to >=4.
• cd macros && make sky130_sram_1rw_tiny (or any testcase, which triggers one of the following hidden errors)

Expected behavior

• ERROR messages should always be visible - also on the default loglevel.
• An error should stop execution.

Logs For example, I encountered this error a few dozen times:

Error:  Asymmetric device with multiple terminals!
Error:  Asymmetric device with multiple terminals!
Error:  Asymmetric device with multiple terminals!
Error:  Asymmetric device with multiple terminals!
...

or some of these:

Error while reading cell "sky130_fd_bd_sram__sram_sp_rowend_replica_ce" (byte position 468804): Unknown layer/datatype in boundary, layer=92 type=44
Error while reading cell "sky130_fd_bd_sram__sram_sp_rowend_replica_ce" (byte position 469220): Unknown layer/datatype in boundary, layer=22 type=21
Error while reading cell "sky130_fd_bd_sram__sram_sp_rowend_replica_ce" (byte position 469444): Unknown layer/datatype in boundary, layer=115 type=42
Error while reading cell "sky130_fd_bd_sram__sram_sp_rowend_replica_ce" (byte position 469572): Unknown layer/datatype in boundary, layer=115 type=43

Suggestions

• If these are, in fact, errors, they should not be hidden in the default log level.
• If these are not errors, they could be renamed to (critical) warnings.