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

Hunting for nondeterminism in our tools #209

Open
PeterMatula opened this issue Feb 8, 2018 · 1 comment
Open

Hunting for nondeterminism in our tools #209

PeterMatula opened this issue Feb 8, 2018 · 1 comment

Comments

@PeterMatula
Copy link
Collaborator

From time to time, we notice nondeterminism in some of our tools. We try to fix it once it is identified. It would be nice to be able to automatically and periodically test for it. We should ideally test:

  • Diffs in several runs of the same build.
  • Diffs in runs of different builds (compilers, options, etc.).
  • Diffs in runs on different systems (Linux/Windows).
    Moreover, there might be some inherent nondeterminisms - time stamps, absolute paths, etc.

Right now, I have no idea how to do something like this. If anyone have any suggestion, please comment.

PeterMatula added a commit to avast/retdec-regression-tests that referenced this issue Aug 23, 2018
They are timeouting after 1200 seconds. It looks like there is some nondeterminism going on, because one of them (my-printf-decompilation-quality) did successfully run (once) when run manually on macOS server. There are slight differences between *.ll produces on macOS server and my Linux. Related to avast/retdec#209.
@PeterMatula
Copy link
Collaborator Author

PeterMatula commented Sep 12, 2018

Commits disabling regression tests on macOS due to non-determinism:

Enable these when solved.

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

No branches or pull requests

1 participant