I knew this could happen in theory, but I didn't think it would actually occur in practice. Well, clearly it does, though I've only seen this on my laptop. I assume the console printing may occassionally take long enough to affect the output on older machines.
The fix is trivial: Simply overwrite the time (stored in the primitive itself) after running the scenario to ensure it's always the same.
I knew this could happen in theory, but I didn't think it would actually occur in practice. Well, clearly it does, though I've only seen this on my laptop. I assume the console printing may occassionally take long enough to affect the output on older machines.
The fix is trivial: Simply overwrite the time (stored in the primitive itself) after running the scenario to ensure it's always the same.