-
Notifications
You must be signed in to change notification settings - Fork 201
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
Record state count info in manifest, check during CI #122
Conversation
Signed-off-by: Andrew Helwer <2n8rn1w1f@mozmail.com>
Signed-off-by: Andrew Helwer <2n8rn1w1f@mozmail.com>
@lemmy is it possible for state depth to vary nondeterministically with TLC or should it always be the same? From the latest CI run: Both Windows & Linux:
Only Windows (check matches on Linux):
Edit: on thinking about it I suspect it is normal for the state depth to vary as in multithreaded TLC a state that could be 12 steps away from the initial state could be discovered earlier or later by a different thread only 10 steps away from the initial state. So I don't think I should record state depth. |
Where do I find TLC's output? |
It is printed out in the CI; here it is for MCVoting.cfg:
Here it is for glowingRaccoon/clean.cfg:
I derived all the state numbers on my local workstation using |
The diameter should be deterministic: |
Signed-off-by: Andrew Helwer <2n8rn1w1f@mozmail.com>
Signed-off-by: Andrew Helwer <2n8rn1w1f@mozmail.com>
Signed-off-by: Andrew Helwer <2n8rn1w1f@mozmail.com>
Quite nice having this data in the manifest actually, there are some interesting numbers in there especially with regard to state depth.
Record but temporarily disable state depth/diameter check due to tlaplus/tlaplus#883
Closes #120
Also deactivate macOS CI, ref #119