-
Notifications
You must be signed in to change notification settings - Fork 131
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
Try a backup copy if the downloaded cutechess-cli is not working. #1369
Conversation
ce22912
to
f347358
Compare
0d30dcc
to
434fce3
Compare
@ppigazzini I wonder if you could have a look at this PR? I think it is a nice refactoring of the setup of cutechess-cli. Perhaps it might also deal correctly with this issue (if it is solvable at all): https://tests.stockfishchess.org/actions?action=&user=technologov&before=1657958686.643&count=100 |
f63ee39
to
9d2a2d1
Compare
Last push just moves a comment. No functional change. |
Tested working on WLS and MSYS2 with all the combinations of:
If I'm not wrong the error messages are now only worker side. |
Yes that is true. But IMHO checking that cutechess is working is part of the start up of the worker (like selecting a compiler). |
I meant that I don't view entries in Events log about cutechess-cli problems: I agree that worker.py is the right module for the cutechess-cli check. This the output worker side:
|
The messages in the event log come from failed tasks. In this PR the check for a working cutechess-cli is done before a task is started. So there are no messages in the event log. My plan is to create a log api to post messages to the event log not associated with a task. |
A collateral problem found during the tests of this PR. If we add at example the support for ARM (eg the link to the |
I agree! So the update test should also be done a startup…. |
Latest push does an update test before checking cutechess. |
Logic: 1) Check if cutechess-cli exists and is working. 2) If not: download it. 3) Check if downloaded cutechess-cli is working. 4) If not: try to restore a backup copy. 5) If successful check if the backup copy is working. 6) If not: bail out. Do not treat MacOS specially in the updater. Move cutechess-cli setup to worker.py so that it is done only once.
Nice improvement, thank you @vdbergh :) PS: please try to update PS2: I installed several python tools with |
Logic:
Check if cutechess-cli exists and is working.
If not: download it.
Check if downloaded cutechess-cli is working.
If not: try to restore a backup copy.
If successful check if the backup copy is working.
If not: bail out.
Also: do not treat MacOS specially in the updater.
Also: only setup/verify during worker startup.
Solves #1368 .