Re: nightly build make check etc

Bruno Haible writes:
 > Don Cohen writes:
 > >  > the only reliable indicator is the `make` exist status.
 > > 
 > > perhaps that result could be printed?
 > 
 > When you run "../configure --cbcx", it creates log files
 > cbcstep1.log ... cbcstep6.log, and each of these files ends in a line
 > such as
 >   ===> make extracheck SUCCEEDED
 > or
 >   ===> make extracheck FAILED
 > 
 > It's easy to grep for.

I see it also ends with a summary:

  Bye.
  Makefile:2407: recipe for target 'full-mod-check' failed
  make: *** [full-mod-check] Error 1
  ===> make full-mod-check FAILED
  Step 1 ===> /bin/sh ../src/configure --disable-option-checking --disable-maintainer-mode --cache-file=config.cache SUCCEEDED
  Step 2 ===> make SUCCEEDED
  Step 3 ===> make check FAILED
  Step 4 ===> make extracheck SUCCEEDED
  Step 5 ===> make base-mod-check FAILED
  Step 6 ===> make full-mod-check FAILED

But tail cbcstep* seems better for showing what's wrong in each case:
  $ tail cbcstep*
  ==> cbcstep1.log <==
  config.status: creating po/Makefile.in
  config.status: creating gllib/Makefile
  config.status: creating makemake
  config.status: creating config.h
  config.status: executing depfiles commands
  config.status: executing libtool commands
  config.status: executing po-directories commands
  config.status: creating po/POTFILES
  config.status: creating po/Makefile
  ===> /bin/sh ../src/configure --disable-option-checking --disable-maintainer-mode --cache-file=config.cache SUCCEEDED

  ==> cbcstep2.log <==
  1815980 ;
  167664 ;
  2 ;
  356064 ;
  31679
  grep "^REPLACE_.*='1'" `find . -name config.log` || true
  ./config.log:REPLACE_IOCTL='1'
  ./config.log:REPLACE_MBRTOWC='1'
  ./config.log:REPLACE_STRERROR_R='1'
  ===> make SUCCEEDED

  ==> cbcstep3.log <==
  Test failed:
  -rw-r--r--. 1 don don 188 Jan 24 14:33 streams.erg
  To see which tests failed, type
      cat /home/don/hg/clisp/build-dir/tests/*.erg

I suppose I could just do that cat unconditionally at the end.


  Makefile:34: recipe for target 'compare' failed
  make[1]: *** [compare] Error 1
  make[1]: Leaving directory '/home/don/hg/clisp/build-dir/tests'
  Makefile:2218: recipe for target 'check-tests' failed
  make: *** [check-tests] Error 2
  ===> make check FAILED

It's interesting that this doesn't show the same error I got before
from make check.  I wonder why not.

  ==> cbcstep4.log <==
  if ./image; then exit 1; fi
  STACK size: 98238 [0x180000bfe00 0x18000000010]
  *** - myerror
  ls -l lisp.run lispinit.mem image image.mem
  -rwxrwxr-x. 1 don don 9890592 Jan 24 14:33 image
  -rw-r--r--. 1 don don 3353376 Jan 24 14:33 image.mem
  -rw-r--r--. 1 don don 3357376 Jan 24 14:32 lispinit.mem
  -rwxrwxr-x. 1 don don 6532472 Jan 24 14:31 lisp.run
  rm -f image image.mem
  ===> make extracheck SUCCEEDED

Ah, that was what I wanted to know.  Thanks.

  ==> cbcstep5.log <==
  RUN-TEST: finished #P"/home/don/hg/clisp/modules/readline/test.tst" (0 errors out of 37 tests)
  finished   4 files:               3 errors out of     632 tests
    1             i18n/test.tst:    0 errors out of      11 tests
    2         syscalls/test.tst:    3 errors out of     264 tests
    3           regexp/test.tst:    0 errors out of     320 tests
    4         readline/test.tst:    0 errors out of      37 tests
  Bye.
  Makefile:2403: recipe for target 'base-mod-check' failed
  make: *** [base-mod-check] Error 1
  ===> make base-mod-check FAILED

So now I'd really like to cat syscalls/test.erg


  ==> cbcstep6.log <==
  NIL
  EQL-OK: T
  *** - READ from
        #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/home/don/hg/clisp/modules/rawsock/test.tst" @24>
        : #<PACKAGE RAWSOCK> has no external symbol with name "CONVERT-ADDRESS"

  Bye.
  Makefile:2407: recipe for target 'full-mod-check' failed
  make: *** [full-mod-check] Error 1
  ===> make full-mod-check FAILED

I guess I've never done the full-mod-check.  Sam only asked for mod-check.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel