-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sometimes raises are not called #59
Comments
Not sure if this is only isolated to
There's probably a simple way to check for this in the transaction manager. It might be good to add a bot test, if easy/possible, to protect against this. |
82: Add tournament play fuzz test back in r=charleskawczynski a=charleskawczynski I was trying to reproduce #59, but I'm not seeing it anymore. It may have been eliminated from all of the fixups with `folder` -> `active`/`still_playing` changes. Co-authored-by: Charles Kawczynski <kawczynski.charles@gmail.com>
Hmm, raises don't always need to be called, and I'm not seeing this error anymore. Closing for now. |
Okay, okay, there is still a bug. Good news though, I think I have a dev branch where I’m tracking down the problems. |
I think this was closed by #85. We'll reopen if that's not the case. |
As of #58, there is a relatively rare bug (1 in ~1000 games?) that is caught from the fuzz tests. Here is the log:
It seems that the first issue here is that the
Bot5050[2]
raise to166.0.
is not called byBot5050[1]
. This demos something we can check for: if all BRs are equal to start, then any all-in should lead to everyone (still playing) being all in.The text was updated successfully, but these errors were encountered: