Hi Peter, > > > > Any preference? I can do either, though I think that after will be easier. > > Either is great!
I have made some local updates (minor stuff including updating the wiki docs), but I won't push and release until tomorrow (20080630). So if anybody else has some more changes, please push before last evening EST time. > > I seem to recall I pushed some new test-suite for gnetlist. I believe a > few tests fail, and we'll need to decide if this is allowed or not. (And > if we want, update the golden files). Yeah, I see these failures too. Here are the failures on my machine: All backends = allegro bae bom2 bom calay cascade drc2 drc eagle futurenet2 geda gossip gsch2pcb mathematica maxascii osmond pads partslist1 partslist2 partslist3 PCBboard pcbpins PCB protelII redac spice spice-sdb switcap systemc tango vams verilog vhdl vipec Running tests on backend "allegro" Running tests on backend "bae" Running tests on backend "bom2" Running tests on backend "bom" Running tests on backend "calay" Running tests on backend "cascade" Running tests on backend "drc2" FAILED: run_backend_test.sh returned 5 failures Running tests on backend "drc" Running tests on backend "eagle" Running tests on backend "futurenet2" Running tests on backend "geda" Running tests on backend "gossip" Running tests on backend "gsch2pcb" Running tests on backend "mathematica" Running tests on backend "maxascii" Running tests on backend "osmond" Running tests on backend "pads" Running tests on backend "partslist1" Running tests on backend "partslist2" Running tests on backend "partslist3" Running tests on backend "PCBboard" FAILED: run_backend_test.sh returned 1 failures Running tests on backend "pcbpins" Running tests on backend "PCB" Running tests on backend "protelII" Running tests on backend "redac" Running tests on backend "spice" FAILED: run_backend_test.sh returned 2 failures Running tests on backend "spice-sdb" Running tests on backend "switcap" Running tests on backend "systemc" Running tests on backend "tango" Running tests on backend "vams" Running tests on backend "verilog" Running tests on backend "vhdl" Running tests on backend "vipec" Passed 31, failed 3, out of 34 tests. FAIL: run_tests.sh =================== 1 of 1 tests failed =================== 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)? Thanks, -Ales PS. Many thanks to DJ and his family for hosting us for today's code sprint/BBQ. I got a whole slew of administration tasks done. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
