Simon Marlow wrote,
Simon Peyton-Jones wrote:
| I understand that incremental builds are more tricky, but during
| teaching session I often have only 2 hours to hack on a day.
I'm still hopeful that a "last-good-build" date or
signature-of-some-kind should do the job. Ideally it goes like thi
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/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Thu May 31 19:30:01 BST 2007.
checki
Thu May 31 08:44:32 PDT 2007 Michael D. Adams <[EMAIL PROTECTED]>
* Test for Trac #1396
M ./tests/ghc-regress/gadt/all.T +3
A ./tests/ghc-regress/gadt/gadt24.hs
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listi
Stefan O'Rear wrote:
On Thu, May 31, 2007 at 02:54:13PM +0100, Simon Marlow wrote:
Neil Mitchell wrote:
Hi
The disadvantage is that you need quite a bit of disk space, and that
if a buildbot is dead for a long time the "works" tree may get quite
old.
I wondered about this too, but I was worry
On Thu, May 31, 2007 at 02:54:13PM +0100, Simon Marlow wrote:
> Neil Mitchell wrote:
> >Hi
> >
> >>> The disadvantage is that you need quite a bit of disk space, and that
> >>> if a buildbot is dead for a long time the "works" tree may get quite
> >>> old.
> >>
> >>I wondered about this too, but I
Neil Mitchell wrote:
Hi
> The disadvantage is that you need quite a bit of disk space, and that
> if a buildbot is dead for a long time the "works" tree may get quite
> old.
I wondered about this too, but I was worrying about ensuring atomicity
during
the push, especially since we have multip
Hi
> The disadvantage is that you need quite a bit of disk space, and that
> if a buildbot is dead for a long time the "works" tree may get quite
> old.
I wondered about this too, but I was worrying about ensuring atomicity during
the push, especially since we have multiple repos. Maybe it's n
Thu May 31 06:41:13 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* fix locations for uploading src dists
M ./Makefile -4 +4
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Thu May 31 06:28:42 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX unregisterised build
Can't check $(GhcUnregisterised) eagerly, because it might not have
been set yet (it's set in build.mk).
M ./mk/config.mk.in -3 +3
___
Cvs-ghc mailing li
Neil Mitchell wrote:
Hi
> Or am I being naive?
date/time doesn't work well with darcs. Consider the case where we
have a
successful build on date T, and then someone sent us a patch P that they
recorded before T. We push the patch, and now "all the patches up to
date T"
includes P, but it
Hi
> Or am I being naive?
date/time doesn't work well with darcs. Consider the case where we have a
successful build on date T, and then someone sent us a patch P that they
recorded before T. We push the patch, and now "all the patches up to date T"
includes P, but it didn't when we did the b
Simon Peyton-Jones wrote:
| I understand that incremental builds are more tricky, but during
| teaching session I often have only 2 hours to hack on a day.
I'm still hopeful that a "last-good-build" date or signature-of-some-kind
should do the job. Ideally it goes like this
* Look at GHC dev
| I understand that incremental builds are more tricky, but during
| teaching session I often have only 2 hours to hack on a day.
I'm still hopeful that a "last-good-build" date or signature-of-some-kind
should do the job. Ideally it goes like this
* Look at GHC dev wiki, get last-good-build si
Thu May 31 04:05:06 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX: loading package ghc in GHCi (added a couple of missing symbols)
M ./rts/Linker.c +2
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-g
Simon Marlow wrote,
Manuel M T Chakravarty wrote:
In the last couple of weeks I spent a lot of time just trying to
compile GHC. With the constantly changing build system, incremental
builds fail more often than not after new patches are pulled. And
sometimes even clean builds don't work. Fo
GHC Build Reports wrote:
[3 of 5] Compiling Language.Haskell.TH.Ppr ( Language/Haskell/TH/Ppr.hs,
dist/build/Language/Haskell/TH/Ppr.o )
[4 of 5] Compiling Language.Haskell.TH.Lib ( Language/Haskell/TH/Lib.hs,
dist/build/Language/Haskell/TH/Lib.o )
[5 of 5] Compiling Language.Haskell.TH ( Lang
Build results:
x86-64 Linux head: fail (failed stage1)
x86 Windows head: fail (failed stage1)
x86 Windows head fast: fail (failed stage1) fail (failed stage1) pass pass lost
pass
Old unexpected test passes:
arith008 1 x86 Windows head
Old unexpected test failures:
GMapAssoc
17 matches
Mail list logo
