Thanks again for your clear explanations. 2007/12/8, Gunnar Farnebäck <[EMAIL PROTECTED]>: > > But in this case if we accept a failure we can miss eventually > > a bigger mistake of GNU Go if the result become for example > > > > 1 FAILED: Correct '1 1 (PASS|A9|C9)', got '0 0 F9' > > > > How can we manage this risk? > > One possibility is to include a relaxed test which doesn't check the > move, using a regexp like > #? [1 1 (.*)]
I'll use this workaround to refine the test suite STS-RV and I will add a note about. The file STS-RV_0.tst is already emended: http://trac.gnugo.org/gnugo/ticket/41 Thanks -- Emanuele http://www.google.com/reader/shared/07971903590737268053 _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
