I made an error, I drew a circle in the F.Cu layer instead of F.Silkscreen. It cuts through several traces. Thereby shorting some nets.
I found out after board manufacturing.
I’m very surprised the DRC did not complain. Is this a feature that I have to enable? Or am I missing something?
I’m not sure why “Test for parity between PCB and schematic” would be relevant in this case. Older versions of KiCad just ignored graphics (I assume your circle is a graphic entity) but checks for clearances between tracks and graphics on a copper layer was introduced in V5.99 as far as I can remember, which means all V6 versions should have it.
There is a possibility to ignore any and all DRC violations in PCB Editor / File / Board Setup / Design Rules / Violation Severity. I don’t see a separate item for clearance between tracks and graphics, it’s all under the umbrella of “Clearance Violation”.
I also agree with mv_ibfeew and davidrsb. Version bumps in the third digit should always be safe to upgrade. There was a *&^%$#@! some time ago with V6.0.3 and therefore it is not even listed on KiCad’s website:
That version had a Huge bug in it and was removed a few days after release, but it is a reminder to wait a week or so with updating if your income depends on KiCad.
If you can’t reproduce this in V6.0.9, then it would be nice if you can make a copy of the project, remove most of the schematic and PCB (just the footprint and some tracks connecting it to something else is best), and then zip it up and post it here, for further examination.
I had a similar mistake many years ago with another CAD tool. That’s when I learned that one of the key steps in the mfg process is “always-always-always look at your gerbers”. Later I found a proggy that takes your gerbers as input and compares them to your IPC netlist. It was called FAB3000 by Numerical Innovations. It’s not clear to me that they still exist or if their product is still affordable. There may be others.
This is certainly a bug, and a strange one. There’s something in this specific circle instance. If I delete it and create a new one, the DRC finds the error. But not with this circle. I also moved it and there’s no error: