ThreadDelay is a perfectly reasonable test: it tests that threadDelay doesn't wait for *less* time than was requested. Clearly something is wrong on your machine with either threadDelay or the way time is measured, but we haven't seen the same symptoms elsewhere so it's hard to diagnose. Still, we should try to investigate at some point.
oops, sorry. on looking through the test sources, it seems i was thinking of CPUTime, which also fails occasionally if my laptop is loaded.
there's a comment in GHC.Conc: -- Note: threadDelay, threadWaitRead and threadWaitWrite aren't really functional -- on Win32, but left in there because lib code (still) uses them (the manner -- in which they're used doesn't cause problems on a Win32 platform though.) is that (still) relevant? claus _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
