gEDA-bug: [Bug 698743] Re: drc2 backend should check that NoConnection nets

[Alan Somers <698743@xxxxxxxxxxxxxxxxxx>]

Uploaded new patch.  This patch updates the drc2 regression test results
to account for the extra line in drc2's output.  Only one test has an
interesting change: net-not-driven-with-nc-directive has an additional
error now.  That error is intentional: the circuit has two connected
pins marked as NoConnection.  The patch also fixes two spelling errors
in the text output of run_tests.sh

** Patch added: "0001-Fixed-regression-tests-to-account-for-new-connected-.patch"
   https://bugs.launchpad.net/geda/+bug/698743/+attachment/1788752/+files/0001-Fixed-regression-tests-to-account-for-new-connected-.patch

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/698743

Title:
  drc2 backend should check that NoConnection nets

Status in GPL Electronic Design Automation tools:
  In Progress

Bug description:
  Adding the NoConnection DRC attribute to a net causes the drc2 backend to ignore it when checking for unconnected nets.  However, drc2 currently doesn't enforce that the net is actually unconnected.  It's possible to mark two pins as NoConnection and then accidentally wire them together.  This patch to gnet-drc2.scm checks for that case.




_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug