Maxim Masiutin

> done @sebres Thank you, however, the regex was incomplete, I have addressed this issue in the pull request to update the regex to work on a real Dante server...

@vdbergh Thank you very much by accepting my proposal and writing proper code! Your objections were more than reasonable, I also thought about implementing them since I didn't like lots...

Yes, I agree, thank you @vdbergh on your observation that we should aim to avoid worker changes. If the worker is already able to display a full message received from...

Now this pull request contains the updates made by @dubslow via https://github.com/maximmasiutin/fishtest/pull/4/commits

There are pros and cons of formatting the message on the worker vs formatting it on the server. If the message is formed by the server, than the worker will...

> That's exactly the stuff that has to be updated in the worker every time we add a new reason or change No, @dubslow - the worker can just enumerate...

> > There may be cases where simple benchmarking would not give result, i.e. in multithreading > > I disagree with this. Just benchmark with multiple threads. Why do benchmarks...

> a few hundred thousand, yea OK, I will run 800000 games, TC 60s+0.6s, 16 threads:

@Disservin wrote: >That’s not even the fishtest limit for LTC SMP tests! The test will probably finish faster, yielding results (positive or negative) sooner than that limit, I hope. >The...

I'm using cutechess-cli with `-tb` parameter to give cutechess the Syzygy tablebases for adjudication; however, the engines are not using the tablebases. They just help cutechess-cli decide the winner faster...