<div>Terrible! Quite sorry that this seems to be a bug in the monad-par library.</div><div><br></div>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? In the meantime, it's good that you can at least run without parallelism.<div>
<br></div><div>Best,</div><div> -Ryan<br><br><div class="gmail_quote">On Sun, Aug 12, 2012 at 11:20 AM, Aleksey Khudyakov <span dir="ltr"><<a href="mailto:alexey.skladnoy@gmail.com" target="_blank">alexey.skladnoy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 10.08.2012 22:20, Till Berger wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So I am not sure if this is a bug in Criterion itself, the Statistics<br>
package or any dependency or if I am doing something obviously wrong. I<br>
would be grateful if someone could look into this as it is holding me<br>
back from using Criterion for benchmarking my code.<br>
<br>
</blockquote>
I would suspect Statistics.Resampling.<u></u>resample. From quick glance<br>
criterion doesn't use any concurrent stuff. I'll try create smaller test<br>
case<br>
</blockquote>
<br>
It looks like I'm wrong. I obtained event log from crashing program<br>
and resample completed its work without problems. Crash occured later.<br>
Next<br>
suspect is bootstrapBCA itself. It uses monad-par to obtain<br>
parallelism[1].<br>
<br>
I tried to create smaller test case without any success.<br>
<br>
<br>
<br>
[1]<br>
<a href="https://github.com/bos/statistics/blob/master/Statistics/Resampling/Bootstrap.hs#L84" target="_blank">https://github.com/bos/<u></u>statistics/blob/master/<u></u>Statistics/Resampling/<u></u>Bootstrap.hs#L84</a><br>
<br>
</blockquote>
<br>
Replacing "runPar $ parMap" with a simple "map" on that line seems to<br>
fix the bug. At least I could not reproduce it anymore on several runs<br>
with my original test case. So it seems to be a bug in the Par monad<br>
package as this change shouldn't alter the program's behaviour, should it?<br>
<br>
</blockquote></div>
Looks like this is the case. But reducing test case to reasonable size (e.g. removing most of criterion and statistics could be quite difficult<div><div><br>
<br>
______________________________<u></u>_________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/<u></u>mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div>