The dummy functions are using a global "random oracle" module in which all the modules are sharing the same pseudorandom number generator. Before, dummy_values.ml was generated at compile time hence wasn't competing for a given seed state with the other functions. This PR restores that
NOTE: We should definitely get rid of the global random oracle state in follow up work. I'm surprised it hasn't caused more problems in the past -- in theory the order in which you run the tests can break them
The
dummy
functions are using a global "random oracle" module in which all the modules are sharing the same pseudorandom number generator. Before,dummy_values.ml
was generated at compile time hence wasn't competing for a given seed state with the other functions. This PR restores thatNOTE: We should definitely get rid of the global random oracle state in follow up work. I'm surprised it hasn't caused more problems in the past -- in theory the order in which you run the tests can break them