Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving reproducibility in verrou_dd #16

Open
HadrienG2 opened this issue Jul 8, 2018 · 1 comment
Open

Improving reproducibility in verrou_dd #16

HadrienG2 opened this issue Jul 8, 2018 · 1 comment

Comments

@HadrienG2
Copy link
Contributor

HadrienG2 commented Jul 8, 2018

Debugging rare failures with verrou_dd can be very difficult. Either you are lucky and the failure can be reproduced in upward/downward rounding mode, or you are in for a long time tuning VERROU_DD_NRUNS, potentially to absurdly high values, without managing to reproduce the failure on every run.

Farthest does not always help because its result not stable under delta-debugging (as it depends on previous rounding decisions), and I suspect that this also holds for toward_zero. Similarly, vr-seed does not help reprodubility in delta-debugging mode, because it only reproduces the sequence of roundings that will be applied, and not the places where they will be applied.

I think this could be improved, admittedly at the cost of large overhead (which may prove intractable in practice), by recording the sequence of rounding modes that was applied on each source file location, and reproducing that instead of just the global random number sequence.

@wkirschenmann
Copy link

Maybe another approach would be to store the RNG state while entering each block. Still big but probably more manageable. Another solution would be to rely on hellgrind to ensure a deterministic order of blocs executions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants