search (bug): null move returned while pondering about mess HOT 6 OPEN

Mess's pondering is probably a bit bugged right now. From the logs, it seems like Mess received the ponderhit command extremely fast after the go ponder. It probably wasn't able to start a search before the ponderhit command was received. That said, this issue needs some investigation. Thank you for the information.

from mess.

@tissatussa Could you provide the average nps which Mess was reporting during this tournament?

from mess.

it was not a tournament, it was a single game .. i showed the tail log lines, it's all i have .. mess does not output extensive info lines, like the opponent, having nps data .. however, running another game (6m3s) from normal starting position, mess DOES output such info lines and so i see an nps around 700000 upto 1 milion ..

from mess.

With 1 Mnps, the issue of the ponderhit command arriving too fast can be discarded. The main issue which I see is that Mess was not reporting info properly for some reason, which is weird since it does print an info string for each depth it completes. This suggests that there was some misconfiguration when setting up the problematic game, though I have no idea what. Please do report if this occurs again.

from mess.

Please do report if this occurs again

OK, i will do that.

btw. i do not always use Ponder -- it's a checkbox in CuteChess called "Thinking on opponent's time", but not all engines support it. I remember that game had Ponder ON. Might the Ponder option have been the cause of the problem ? Or do you have no clue ?

from mess.

btw. i do not always use Ponder -- it's a checkbox in CuteChess called "Thinking on opponent's time", but not all engines support it. I remember that game had Ponder ON. Might the Ponder option have been the cause of the problem ? Or do you have no clue ?

As I said:

Mess's pondering is probably a bit bugged right now.

So yeah, probably.

from mess.