ANNOUNCE: GHC 6.12.3 Release Candidate 1
kili at outback.escape.de
Sat May 29 10:07:40 EDT 2010
On Fri, May 28, 2010 at 10:05:36PM +0100, Simon Marlow wrote:
> > hReady002(ghci)
> > ==> did not investigate yet. failure details below
> This one is a known failure right now (I need to clean it up).
Good to know. Thanks for the info.
> > num009(normal,optc,hpc,optasm,ghci)
> > ==> no idea. failure details below
If in doubt, suspect OpenBSD here; this is not the first time I've
seen strange differences between our math and the math on other
systems. But it's reall strange that there are different failures
for different ways. I'll try to find what's going on.
> > signals002(normal,optc,hpc,optasm,ghci)
> > ==> wrong exit code (150, expected 0). not yet investigated.
> Could be that signals are being delivered too quickly and overflowing
> the IO manager's pipe. We see this failure on our x86/Linux box too,
> but not on x86_64. Summary: if it's lost signals due to the pipe
> filling up, it's a known issue.
Also good to know. I'll have a closer look wether it's the problem
you mention (but I'm still short of time, so this may have to wait).
As always, please don't let any problems specific to OpenBSD delay
More information about the Glasgow-haskell-users