Hi John,

Thanks for the hints/reply.  The best seems to go with 7.2 and I
could just wait for v7.2 no problem -- there is no rush ;-)  Moreover
since package now got stuck in the NEW queue - I do not even know what
would be results on the other platforms... I could try on a local sparc
box meanwhile if you are interested... ?

Cheers,

On Fri, 01 Feb 2013, John Langford wrote:

> I think you must enable fuzzy match in RunTests as in the base Makefile:

> (cd test && ./RunTests -d -fe -E 0.001 ../vowpalwabbit/vw
> ../vowpalwabbit/vw)

> The difficulty here is that slightly different things happen
> depending on architecture due to using (for example) -ffast-math
> with floating point.

> Looking through the logs, this will help but not eliminate the
> problem because some of the more advanced algorithms make hard
> decisions based on soft float values.   In the current master
> branch, this is addressed by using --quiet with some of the tests.
> If you want to go with that, I could drop a v7.2 for your use.

> -John

> On 01/28/2013 02:34 PM, Yaroslav Halchenko wrote:
> >Hi John (and Pieter),

> >I have uploaded vw 7.1 to Debian experimental.  There it will need to go
> >through Debian NEW queue since now it carries all those packages for the
> >libraries, and I placed tests as examples into -doc package.

> >I also uploaded backport builds (where built) to neuro.debian.net
> >repository:

> >vowpal-wabbit_7.1-1~nd60+1_i386.build   FAILED  1:28.80 real, 64.41 user, 
> >40.19 sys, 565784 out
> >vowpal-wabbit_7.1-1~nd60+1_amd64.build  FAILED  1:26.48 real, 68.37 user, 
> >40.93 sys, 707968 out
> >vowpal-wabbit_7.1-1~nd70+1_i386.build   OK      6:18.24 real, 324.79 user, 
> >74.82 sys, 1627008 out
> >vowpal-wabbit_7.1-1~nd70+1_amd64.build  OK      6:05.29 real, 333.92 user, 
> >78.22 sys, 2437168 out
> >vowpal-wabbit_7.1-1~nd+1_i386.build     OK      6:17.74 real, 327.47 user, 
> >72.99 sys, 1644344 out
> >vowpal-wabbit_7.1-1~nd+1_amd64.build    OK      3:26.17 real, 188.32 user, 
> >67.79 sys, 1930168 out
> >vowpal-wabbit_7.1-1~nd10.10+1_i386.build        FAILED  1:03.92 real, 73.74 
> >user, 36.76 sys, 63632 out
> >vowpal-wabbit_7.1-1~nd10.10+1_amd64.build       FAILED  0:55.09 real, 73.55 
> >user, 36.32 sys, 72736 out
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build        OK      7:23.65 real, 328.56 
> >user, 286.50 sys, 1269520 out
> >vowpal-wabbit_7.1-1~nd10.04+1_amd64.build       OK      7:27.87 real, 326.37 
> >user, 314.68 sys, 1934032 out
> >vowpal-wabbit_7.1-1~nd11.04+1_i386.build        FAILED  2:21.23 real, 118.42 
> >user, 57.73 sys, 566712 out
> >vowpal-wabbit_7.1-1~nd11.04+1_amd64.build       FAILED  2:19.85 real, 119.40 
> >user, 60.94 sys, 709336 out
> >vowpal-wabbit_7.1-1~nd11.10+1_i386.build        FAILED  2:07.75 real, 99.89 
> >user, 59.27 sys, 563752 out
> >vowpal-wabbit_7.1-1~nd11.10+1_amd64.build       FAILED  2:08.01 real, 101.94 
> >user, 63.75 sys, 855024 out
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build        OK      5:56.08 real, 323.54 
> >user, 90.53 sys, 1388112 out
> >vowpal-wabbit_7.1-1~nd12.04+1_amd64.build       OK      6:01.30 real, 339.88 
> >user, 99.06 sys, 2253736 out
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build        OK      6:25.92 real, 346.61 
> >user, 87.57 sys, 1585144 out
> >vowpal-wabbit_7.1-1~nd12.10+1_amd64.build       OK      6:35.52 real, 358.59 
> >user, 93.55 sys, 2395912 out

> >if needed -- would fix for those failed ones (my bad).
> >But that also showed problems with tests on all 32bit builds:

> >neurodebian@head2:~/deb/builds/vowpal-wabbit/7.1-1$ grep FAILED: *.build
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 12: FAILED: 
> >ref(train-sets/ref/searn_wsj.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 13: FAILED: 
> >ref(train-sets/ref/searn_wsj2.dat.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 16: FAILED: 
> >ref(train-sets/ref/wiki1K.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 17: FAILED: 
> >ref(train-sets/ref/searn_small.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 18: FAILED: 
> >ref(train-sets/ref/3parity.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd10.04+1_i386.build:RunTests: test 20: FAILED: 
> >ref(train-sets/ref/xxor.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 12: FAILED: 
> >ref(train-sets/ref/searn_wsj.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 13: FAILED: 
> >ref(train-sets/ref/searn_wsj2.dat.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 16: FAILED: 
> >ref(train-sets/ref/wiki1K.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 17: FAILED: 
> >ref(train-sets/ref/searn_small.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 18: FAILED: 
> >ref(train-sets/ref/3parity.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.04+1_i386.build:RunTests: test 20: FAILED: 
> >ref(train-sets/ref/xxor.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 12: FAILED: 
> >ref(train-sets/ref/searn_wsj.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 13: FAILED: 
> >ref(train-sets/ref/searn_wsj2.dat.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 16: FAILED: 
> >ref(train-sets/ref/wiki1K.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 17: FAILED: 
> >ref(train-sets/ref/searn_small.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 18: FAILED: 
> >ref(train-sets/ref/3parity.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd12.10+1_i386.build:RunTests: test 20: FAILED: 
> >ref(train-sets/ref/xxor.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 12: FAILED: 
> >ref(train-sets/ref/searn_wsj.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 13: FAILED: 
> >ref(train-sets/ref/searn_wsj2.dat.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 16: FAILED: 
> >ref(train-sets/ref/wiki1K.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 17: FAILED: 
> >ref(train-sets/ref/searn_small.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 18: FAILED: 
> >ref(train-sets/ref/3parity.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd+1_i386.build:RunTests: test 20: FAILED: 
> >ref(train-sets/ref/xxor.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 12: FAILED: 
> >ref(train-sets/ref/searn_wsj.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 13: FAILED: 
> >ref(train-sets/ref/searn_wsj2.dat.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 16: FAILED: 
> >ref(train-sets/ref/wiki1K.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 17: FAILED: 
> >ref(train-sets/ref/searn_small.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 18: FAILED: 
> >ref(train-sets/ref/3parity.stderr) != stderr(stderr.tmp)
> >vowpal-wabbit_7.1-1~nd70+1_i386.build:RunTests: test 20: FAILED: 
> >ref(train-sets/ref/xxor.stderr) != stderr(stderr.tmp)


> >full build logs are available for your consideration at
> >http://neuro.debian.net/_files/_buildlogs/vowpal-wabbit/7.1

> >Cheers,

> >On Sat, 26 Jan 2013, Pieter Ennes wrote:

> >>Package: vowpal-wabbit
> >>Severity: wishlist
> >>Please package the latest 7.1 release of vowpal-wabbit.




-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to