While investigating issue 161, I made some more test runs and discovered, unfortunately, another runtime error (to be exact, two in a row), also transient by nature.
Pathological output:
benchmarking const
time 56.16 ns (56.10 ns .. 56.21 ns)
1.000 R² (1.000 R² .. 1.000 R²)
Error text:
CriterionRight.hs: ./Data/Vector/Generic.hs:245 ((!)): index out of bounds
(-9223372036854775808,1000)
CallStack (from HasCallStack):
error, called at ./Data/Vector/Internal/Check.hs:87:5 in
vector-0.12.0.1-CnPH69pDwM4A5esizlXfXi:Data.Vector.Internal.Check
CriterionRight.hs: thread blocked indefinitely in an MVar operation
These were collected via a simplistic automation script, so I cannot tell exactly how the error and the output should be interleaved. What I can tell is that an error of such pattern happened 36 times during 100 runs.
I'm attaching the log generated by my automation script. The automation script itself can be reviewed in the repository and the measures replicated by the kind reader.
RepeatedlyTest.hs.log
While investigating issue 161, I made some more test runs and discovered, unfortunately, another runtime error (to be exact, two in a row), also transient by nature.
Pathological output:
Error text:
These were collected via a simplistic automation script, so I cannot tell exactly how the error and the output should be interleaved. What I can tell is that an error of such pattern happened 36 times during 100 runs.
I'm attaching the log generated by my automation script. The automation script itself can be reviewed in the repository and the measures replicated by the kind reader.
RepeatedlyTest.hs.log