-
Notifications
You must be signed in to change notification settings - Fork 436
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
recent regression with uci engine #850
Comments
lichess-bot processes debug output even if it isn't enabled, because it stores it in a file inside the What version of |
The commit you revert to is before commit 26732d1. That commit causes lichess-bot to try to start the chess engine on startup as a quick check that the engine is configured correctly. When you revert to the older commit, can your engine actually play a game, or does it exit with an error? |
I spoke too soon: no, it doesn't actually play a game, despite not putting out any debug info (any in the log would be from an earlier run). python-chess version is 1.9.4: maybe that is the issue? |
In your configuration file: uci_options:
Threads: 8
Hash: 32768
SyzygyTbPath: /home/jdart/chess/syzygy:/home/jdart/chess/syzygy-6man/wdl:/home/jdart/chess/syzygy-6man/dtz
debug: true The option
The error happens because your engine does not know what to do with a |
This error is from line 392 of the log you posted:
|
Ok, thanks. |
Describe the bug
after updating to the HEAD, lichess-bot fails on startup with an exception. This appears to be a recent behavior change: If I revert back to commit 616dd81, it works. Note I have filed a similar issue with python-chess (niklasf/python-chess#1049) but I believe this is a different problem, because it occurs without debug output enabled.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
startup of engine, no exception
Logs
lichess.log
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: