On 01.10.2012 02:14, Ben Gamari wrote:
Aleksey Khudyakovalexey.sklad...@gmail.com writes:
On 13.08.2012 19:43, Ryan Newton wrote:
Terrible! Quite sorry that this seems to be a bug in the monad-par library.
I'm copying some of the other monad-par authors and we hopefully can get
to the
Aleksey Khudyakov alexey.sklad...@gmail.com writes:
On 13.08.2012 19:43, Ryan Newton wrote:
Terrible! Quite sorry that this seems to be a bug in the monad-par library.
I'm copying some of the other monad-par authors and we hopefully can get
to the bottom of this. If it's not possible to
Terrible! Quite sorry that this seems to be a bug in the monad-par library.
I'm copying some of the other monad-par authors and we hopefully can get to
the bottom of this. If it's not possible to create a smaller reproducer,
is it possible to share the original test that triggers this problem?
Terrible! Quite sorry that this seems to be a bug in the monad-par library.
I'm copying some of the other monad-par authors and we hopefully can get to
the bottom of this. If it's not possible to create a smaller reproducer,
is it possible to share the original test that triggers this problem?
On 13.08.2012 19:43, Ryan Newton wrote:
Terrible! Quite sorry that this seems to be a bug in the monad-par library.
I'm copying some of the other monad-par authors and we hopefully can get
to the bottom of this. If it's not possible to create a smaller
reproducer, is it possible to share the
On 13.08.2012 20:26, Till Berger wrote:
Terrible! Quite sorry that this seems to be a bug in the monad-par
library.
I'm copying some of the other monad-par authors and we hopefully can
get to
the bottom of this. If it's not possible to create a smaller reproducer,
is it possible to share the
On 10.08.2012 22:20, Till Berger wrote:
So I am not sure if this is a bug in Criterion itself, the Statistics
package or any dependency or if I am doing something obviously wrong. I
would be grateful if someone could look into this as it is holding me
back from using Criterion for benchmarking
So I am not sure if this is a bug in Criterion itself, the Statistics
package or any dependency or if I am doing something obviously wrong. I
would be grateful if someone could look into this as it is holding me
back from using Criterion for benchmarking my code.
I would suspect
On 07.08.2012 19:15, Aleksey Khudyakov wrote:
On 07.08.2012 18:16, Till Berger wrote:
Dear all,
So I am not sure if this is a bug in Criterion itself, the Statistics
package or any dependency or if I am doing something obviously wrong. I
would be grateful if someone could look into this as it
Dear all,
I may have stumbled upon a bug in the Criterion package. When running
the attached Haskell program (Benchmark.hs, a simple test case) on
multiple cores (with +RTS -N, +RTS -N2, +RTS -N3 etc.) it sooner or
later crashes with the following exception:
Benchmark: thread blocked
Hi Till,
This would make an excellent bug report at:
https://github.com/bos/criterion/issues
Cheers,
Johan
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
On 07.08.2012 18:16, Till Berger wrote:
Dear all,
I may have stumbled upon a bug in the Criterion package. When running
the attached Haskell program (Benchmark.hs, a simple test case) on
multiple cores (with +RTS -N, +RTS -N2, +RTS -N3 etc.) it sooner or
later crashes with the following
12 matches
Mail list logo
