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.

Sign up for GitHub

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

Jump to bottom

crashing while running 1000 fixed node test #4

Closed
masterkni6 opened this issue Dec 31, 2020 · 4 comments
Closed

crashing while running 1000 fixed node test #4

masterkni6 opened this issue Dec 31, 2020 · 4 comments

Comments

@masterkni6
Copy link

masterkni6 commented Dec 31, 2020 •
edited
Loading

stacktrace
@masterkni6
Copy link
Author

crashing at real TC 1sec+0.1

stacktrace

@dje-dev
Copy link
Owner

dje-dev commented Jan 1, 2021

It seems that if a search exits immediately (e.g. time exhaustion) then the BestMove is null and this can be dereferenced. However no replication sequence of nodes is obvious. But Ceres should be more defensive in this situation. Related, when presented with a terminal position Ceres aborts upon a "go" command (albeit with a clear message). Consider how to handle this. LC0 responds by outputting an invalid move "bestmove a1a1" which does not seem idea either.

@masterkni6
Copy link
Author

This entire issue may just be a cutechess bug? The current position should have been adjudicated as draw but given to ceres anyways.

Capture

@dje-dev
Copy link
Owner

dje-dev commented Aug 6, 2021

This issue is long since resolved.

@dje-dev dje-dev closed this as completed Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@masterkni6 @dje-dev