Re: [Ocaml-lib-devel] Future of ExtLib

[skaller <sk...@us...>]

On Tue, 2004-12-21 at 07:24, Janne Hellsten wrote:
> Just to inform everyone, I have just imported the testing suite into CVS. 
> The module layout is as proposed by Nicolas.
> 

OK, I import it like this:

My system has the structure:

/usr/local/src/extlib/extlib-dev

So I did this:

cd /usr/local/src/extlib
export CVS_RSH=ssh
cvs -z3 -d:ext:sk...@cv...:/cvsroot/ocaml-lib co
extlib-test

Now I have this:

[skaller@pelican] /usr/local/src/extlib>ls
extlib-dev  extlib-test


[skaller@pelican] /usr/local/src/extlib>ls extlib-test/
CVS       test_Base64.ml   test_ExtString.ml  test_jh_ExtList.ml   
test.mak
Makefile  test_BitSet.ml   test_jh_Base64.ml  test_jh_ExtString.ml 
util.ml
README    test_ExtList.ml  test_jh_BitSet.ml  test_main.ml



[skaller@pelican] /usr/local/src/extlib>cd extlib-test/
/usr/local/src/extlib/extlib-test



[skaller@pelican] /usr/local/src/extlib/extlib-test>make
cd ../extlib-dev && make all
make[1]: Entering directory `/mnt/local/src/extlib/extlib-dev'
ocamlc -a -o extLib.cma enum.mli bitSet.mli dbi.mli dynArray.mli
extHashtbl.mli
extList.mli extString.mli global.mli IO.mli option.mli pMap.mli std.mli
uChar.mli uTF8.mli base64.mli unzip.mli refList.mli optParse.mli
dllist.mli enum.ml bitSet.ml dbi.ml dynArray.ml extHashtbl.ml extList.ml
extString.ml global.ml IO.ml option.ml pMap.ml std.ml uChar.ml uTF8.ml
base64.ml unzip.ml refList.ml optParse.ml dllist.ml extLib.ml
make[1]: Leaving directory `/mnt/local/src/extlib/extlib-dev'
make -f test.mak all
make[1]: Entering directory `/mnt/local/src/extlib/extlib-test'
ocamlc -I ../extlib-dev -g extLib.cma util.ml test_jh_Base64.ml
test_Base64.ml test_jh_BitSet.ml test_BitSet.ml test_jh_ExtList.ml
test_ExtList.ml test_jh_ExtString.ml test_ExtString.ml test_main.ml  -o
extlib_test
make[1]: Leaving directory `/mnt/local/src/extlib/extlib-test'

[skaller@pelican] /usr/local/src/extlib/extlib-test>make run
make -f test.mak run
make[1]: Entering directory `/mnt/local/src/extlib/extlib-test'
./extlib_test
Extlib tester started..
 
run: Base64
run: jh_Base64.test
run: BitSet
run: jh_BitSet.test_intersect
run: jh_BitSet.test_diff
run: jh_BitSet.test_rnd_creation ..FAILED
  reason:
test_jh_BitSet.ml:60:4 test jh_BitSet.test_rnd_creation failed
 
run: jh_BitSet.test_empty
run: jh_BitSet.test_exceptions ..FAILED
  reason:
test_jh_BitSet.ml:116:2 test jh_BitSet.test_exceptions failed

run: ExtString
run: jh_ExtString.t_starts_with
run: jh_ExtString.t_map
run: jh_ExtString.t_lchop
run: jh_ExtString.t_rchop
run: jh_ExtString.t_split
run: ExtList
run: jh_ExtList.iteri
run: jh_ExtList.mapi
run: jh_ExtList.exceptions
run: jh_ExtList.find_exc
All tests completed.
make[1]: Leaving directory `/mnt/local/src/extlib/extlib-test'


All this is expected, including the failures (hmm .. it says
all tests completed, but doesn't report how many faiures .. still
this can be fixed later, for now the important step seems
achieved .. there is a place to put tests and a protocol for
constructing them.

------------------------------------------------------------------------

I added a test for Dynarray (just a stub at the moment).
I got this:

....

Checking in test_main.ml;
/cvsroot/ocaml-lib/extlib-test/test_main.ml,v  <--  test_main.ml
new revision: 1.3; previous revision: 1.2
done
sh: line 1: /cvsroot/ocaml-lib/CVSROOT/commit.log: Permission denied
**********************************************************************

Looks like the commits worked, but the log wasn't updated??

[Comments on test harness next post]

-- 
John Skaller, mailto:sk...@us...
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net