You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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:
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.
The text was updated successfully, but these errors were encountered: