Criterion giving negative measurements in some cases.

I have seen this issue appearing before (#161 , #162), but I am wondering whether this has been fixed permanently or whether there are still some instances where the library will still give negative values.

In my case I cannot post too much information (its company proprietary information), but I am basically running Haxl code in a ghci like environment. Each Haxl module has multiple functions that take in JSON data and spit out some JSON data. I wish to benchmark two things, which involve benchmarking individual functions within these modules as well as benchmarking the running time of the entire module where all the functions run in parallel.

I know this is not much information but if any pointers regarding this issue could be given it would be great! An additional information that I can give without divulging the proprietary code I will try to give to the best of my ability.

Start by reviewing prior issues #161 and #162, then try to reproduce the negative measurements in a GHCi-like environment. Compare benchmarks for individual functions with benchmarks for the full module running functions in parallel; the issue provides no named files or tests, so a concrete reproduction and expected timing behavior would be needed to define done.

Written by the indexing model from the issue text.