pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 238
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/238.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date
Build description = STABLE on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Tue May 10 18:10:01 BST 2011.
checking out new source tree
pgj-freebsd-i386-stable (x86 FreeBSD STABLE), build 221
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-i386-stable/221.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date | S
Full logs at http://log.ouroborus.net/limitingfactor/dph
Environment
Platform
host: limitingfactor.cse.unsw.EDU.AU
arch: i386
processor: i386
system:Darwin 10.7.0
Versions
GHC The Glorious Glasgow Haskell Compilation System, version 7.0.3
GCC i686-apple-da
Build description = HEAD on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Tue May 10 18:00:01 BST 2011.
checking out new source tree
pgj2 (amd64 FreeBSD HEAD), build 356
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/356.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date | Success
booting | Succ
tn23 (x86 OSX HEAD), build 334
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/334.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date | Success
booting | Success
co
pgj (x86 FreeBSD HEAD), build 358
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/358.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date | Success
booting | Success
> File paths that don't decode.
> File paths with a small range of private use characters.
>
> It was always my intention to allow roundtripping of arbitrary
> bytestrings through String. I don't think that the middle ground
> (where you can *read in* a filename without error but not write it out
Build description = STABLE on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx
Nightly build started on cam-04-unx at Tue May 10 18:10:01 BST 2011.
checking out new s
kgardas-opensolaris-x86-head (x86 Solaris HEAD), build 228
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/kgardas-opensolaris-x86-head/228.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date
Build description = HEAD on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Tue May 10 18:00:01 BST 2011.
checking out new source
sparky-unreg (Sparc Solaris unreg HEAD), build 116
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/sparky-unreg/116.html
git clone | Failure: Just (ExitFailure 9)
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/sparky-unreg/116.html
ld.so.1: git: fatal: rel
I found that the runtime stats output was incorrect for the one-line stats
(i.e. the +RTS -t -RTS output). The output was giving zeros for several of the
times, for example the mutator time. The problem was that the time values were
being computed inside a conditional so they were not correctly set
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/2b1b58204204a17781bd39259055cd05000638b3
>---
commit 2b1b58204204a17781bd39259055cd05000638b3
Author: Ian Lynag
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/0449754055f44e87331b1843d3d1ef81bee96452
>---
commit 0449754055f44e87331b1843d3d1ef81bee96452
Author: Ian Lynag
On 10/05/2011 15:29, Max Bolingbroke wrote:
On 18 April 2011 12:48, Simon Marlow wrote:
I'm not sure about the motivation for the factoring here, You've added an
extra member to BufferCodec:
+ recover :: Buffer from -> Buffer to -> IO (Buffer from, Buffer to),
but this always seems to be
On 18 April 2011 12:48, Simon Marlow wrote:
> I'm not sure about the motivation for the factoring here, You've added an
> extra member to BufferCodec:
>
> + recover :: Buffer from -> Buffer to -> IO (Buffer from, Buffer to),
>
> but this always seems to be instantiated by either recoverDecode or
Simon Marlow:
> On 09/05/2011 21:04, Roman Leshchinskiy wrote:
>> As usual, I'm too stupid
>> to understand the git docs. This all *is* quite complicated.
>
> I am also too stupid to understand the git docs. We should start a club!
> What I know about git I've mostly discovered by experimentati
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/1ee923c421b56e9babbfcbc5f635e19e4037a6b8
>---
commit 1ee923c421b56e9babbfcbc5f635e19e4037a6b8
Author: Simon Mar
I have a patch for making mappend = (<>) that I need to port to the
new Git tree. The main reason it hasn't gone in yet is because I
don't know how many client libraries it would break. It was actually
agreed on before 7.0.0 (perhaps even 6.12) but somehow never made it
in.
2011/5/6 Simon Peyton
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/7e0b4417c20ff4afdf66601f2598f7ad0aed923e
>---
commit 7e0b4417c20ff4afdf66601f2598f7ad0aed923e
Author: Simon Mar
On 10/05/2011 11:11, Roman Leshchinskiy wrote:
Simon Marlow wrote:
I'm not sure exactly what it means to rebase two branches "in sync". I
know that if you rebase a branch and the target of the rebase already has
(some of) the patches that you are rebasing, then git will drop them
during the re
Simon Marlow wrote:
>
> I'm not sure exactly what it means to rebase two branches "in sync". I
> know that if you rebase a branch and the target of the rebase already has
> (some of) the patches that you are rebasing, then git will drop them
> during the rebase.
Ah, that's good to know. Thanks! S
Simon and I have just had a chat about the upcoming GHC 7.2 The basic idea for
7.2 is that
· It'll include lots of new code (see below)
· It'll be the first seriously-working release of DPH
· But because of the new code, it may not be a stable as our main
annual releas
On 09/05/2011 21:04, Roman Leshchinskiy wrote:
On 09/05/2011, at 12:34, Manuel M T Chakravarty wrote:
Simon Marlow:
- you develop in your working tree and commit patches there. At
this point it's completely safe to rebase - the patches are only
in one place.
- you pull the patches into the
mbolingbroke (x86 OSX HEAD), build 106
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/mbolingbroke/106.html
git clone | Success
create mk/build.mk| Success
get subrepos | Success
setting version date | Success
booting
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/aa8edc133866d2faaacdde0fee6508562ec580ef
>---
commit aa8edc133866d2faaacdde0fee6508562ec580ef
Author: Simon Pey
28 matches
Mail list logo
