Closed geissdoerfer closed 1 year ago
Hi @geissdoerfer !
Use the ignore_unconnected
option, they go to the same counter: ERROR:Found 0 DRC errors and 9 unconnected pad/s or warnings
Thanks @set-soft that solves my immediate problem. But it will lead to unconnected pads being ignored which is a serious issue that I would absolutely want to make the DRC fail.
Wouldn't it make more sense to pass the DRC with warnings and having something like drc_warnings
to make warnings also fail the DRC, similar to what erc_warnings
does already?
Hi @geissdoerfer ! Warnings were introduced by KiCad 6, KiCad 5 has only violations. You should get 0 warnings, perhaps using exclusions. I'll eventually add correct support for warnings, but this will be a change in behavior, which isn't good. So it must be done carefully.
I was also a bit suprised by this behavior. Would it make sense to keep this issue open as a reminder to improve this?
Wouldn't it make more sense to pass the DRC with warnings and having something like drc_warnings to make warnings also fail the DRC, similar to what erc_warnings does already?
This seems like a good approach (though maybe using something more clear like drc_fail_on_warnings
or something - maybe add erc_fail_on_warnings
as an alias of erc_warnings
as well too?). If compatibility is an issue here, the default value could of course be true (though maybe consider switching the default to false at some point, to be consistent with erc_warnings
?).
Just as a note: this problem is solved by the new KiCad 8 preflights named erc and drc. They use a modern errors classification, and can also generate HTML reports
Running DRC checks on a project that has DRC warnings but no DRC errors fails.
I'm using the KiBot docker image with GitHub Action
v2_k6
with the following kibot_config.yml:Output from the action:
Expected behavior: DRC should pass. This seems to work for the ERC, where there is an explicit option (
erc_warnings
) to treat ERC warnings as errors.