Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com)
Build location    = /playpen/ghc/nightly/HEAD-cam-02-unx
Build config file = /home/v-julsew/nightly/site/msrc/conf-HEAD-cam-02-unx

Nightly build started on cam-02-unx at Wed Jan 21 19:00:01 GMT 2004.
**** checking out new source tree ... ok. (GHC Version 6.3.20040121)
**** Building stage 1 compiler    ... ok.
**** Building stage 2 compiler    ... ok.
**** Building stage 3 compiler    ... ok.
**** building source distribution ... ok.
**** running tests                ... ok (summary below).
**** building binary distribution ... ok.
**** running nofib                ... ok.
**** running nofib                ... ok.
**** running nofib                ... ok. (4 failures)
**** running nofib                ... ok. (4 failures)
**** running nofib                ... ok. (91 failures)
**** publishing distfiles         ... ok.
**** publishing logs              ... ok.
Logs  are at http://www.haskell.org/ghc/dist/current/logs
Dists are at http://www.haskell.org/ghc/dist/current/dist
All done!
Nightly build finished successfully at Thu Jan 22 00:32:33 GMT 2004

------------- GHC Test summary ---------------------

OVERALL SUMMARY for test run started at Wed Jan 21 21:50:59 GMT 2004
    1094 total tests, which gave rise to
    3842 test cases, of which
       0 caused framework failures
     576 were skipped

    3228 expected passes
      24 expected failures
       5 unexpected passes
       9 unexpected failures

Unexpected passes:
   galois_raytrace(optasm)
   tc167(normal)
   tc167(opt)
   tc167(optasm)
   tc167(prof)

Unexpected failures:
   conc018(ghci)
   ghci008(normal)
   hGetBuf001(normal)
   hGetBuf001(ghci)
   mdofail004(normal)
   tc175(normal)
   tc175(opt)
   tc175(optasm)
   tc175(prof)

----------------------------------------------------
Nightly run ended at Thu Jan 22 00:32:33 GMT 2004
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to