On Sun, 2008-06-29 at 22:35 -0400, Ales Hvezda wrote:
> Hi Peter,
> Running tests on backend "drc2"
> FAILED: run_backend_test.sh returned 5 failures
This is due to a change of guile code which means gnetlist no longer
exits with an error code on drc failure. It is a change in behaviour,
but not necessarily a bug.
> Running tests on backend "PCBboard"
> FAILED: run_backend_test.sh returned 1 failures
> Running tests on backend "spice"
> FAILED: run_backend_test.sh returned 2 failures
I can't recall what these were caused by (but the test-suite dumps logs
to look at). Has anyone updated those backends recently?
> Are these consistent with your machine? Also how do I get more information
> on how these tests are failing? In the past, I got the diff right in my
> face showing the exact cause of the failure. What's the best way of
> disabling/fixing these failures (in the short term)?
ls gnetlist/tests/common/*.log has the stdout / stderr logs. The diff is
a little more tricky.
I don't recall the spice-sdb test-suite showing that automagically, and
it was that which I based this common test suite on.
Around line 243:
else
echo "FAILED: See diff -w ${ref} ${out}"
bad=1
I have inserted a call to bash, to drop into a shell and take a poke at
the output files before they get trampled by the next test.
Another way I've worked quite successfully is to have a git checkout
with no changes, then do "./run_tests.sh --regen", and pickup how the
golden files are changed with "git diff".
PS. I'm in Scotland on a field course at the moment, so am not in as
good email contact as usual.
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
