Beta for Stockfish distributed testing

[Ajedrecista]

Hello Jouni:

What is this time control exactly meaning: 60+0.05 th 1?

It is a Fischer time control: each engine starts with 60 seconds and 0.05 seconds are added to its remaining time after each move is played.

I guess that you do not know what 'th 1' is: it means that each engine uses one thread; please take a look at 19th March: you will find 'th 8' and it is explained that each engine used eight threads.

Regards from Spain.

Ajedrecista.

[gladius]

It seems there is a problem with todays version of the client

Code: Select all

  File "worker.py", line 35, in worker
    update()
  File "/home/vdbergh/SRC/CHESS/fishtest/worker/updater.py", line 32, in update
    zip_file = ZipFile(worker_zip)
  File "/usr/lib64/python2.6/zipfile.py", line 696, in __init__
    self._GetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 716, in _GetContents
    self._RealGetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 728, in _RealGetContents
    raise BadZipfile, "File is not a zip file"
BadZipfile: File is not a zip file

I already did a fresh git clone but to no avail.

Hi Michel,

I'm guessing you had an older version of the worker? There was a bug in the updater unfortunately, which caused it to fail, and retry querying github. Github has an API request limit, which is reset every hour. Since you did the fresh git clone, you should be good to go now.

Gary

[Michel]

Unfortunately no. I did a fresh git clone again. As soon as I start the
worker I get

Code: Select all

Exception accessing host:
Traceback (most recent call last):
  File "worker.py", line 35, in worker
    update()
  File "/home/vdbergh/SRC/CHESS/fishtest/worker/updater.py", line 32, in update
    zip_file = ZipFile(worker_zip)
  File "/usr/lib64/python2.6/zipfile.py", line 683, in __init__
    self.fp = open(file, modeDict[mode])
IOError: [Errno 2] No such file or directory: '/home/vdbergh/SRC/CHESS/fishtest/worker/update/wk.zip'

Exception accessing host:
Traceback (most recent call last):
  File "worker.py", line 35, in worker
    update()
  File "/home/vdbergh/SRC/CHESS/fishtest/worker/updater.py", line 32, in update
    zip_file = ZipFile(worker_zip)
  File "/usr/lib64/python2.6/zipfile.py", line 696, in __init__
    self._GetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 716, in _GetContents
    self._RealGetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 728, in _RealGetContents
    raise BadZipfile, "File is not a zip file"
BadZipfile: File is not a zip file

The script worker.py contains the line

WORKER_VERSION = 12

[gladius]

Unfortunately no. I did a fresh git clone again. As soon as I start the
worker I get

Code: Select all

Exception accessing host:
Traceback (most recent call last):
  File "worker.py", line 35, in worker
    update()
  File "/home/vdbergh/SRC/CHESS/fishtest/worker/updater.py", line 32, in update
    zip_file = ZipFile(worker_zip)
  File "/usr/lib64/python2.6/zipfile.py", line 683, in __init__
    self.fp = open(file, modeDict[mode])
IOError: [Errno 2] No such file or directory: '/home/vdbergh/SRC/CHESS/fishtest/worker/update/wk.zip'

Exception accessing host:
Traceback (most recent call last):
  File "worker.py", line 35, in worker
    update()
  File "/home/vdbergh/SRC/CHESS/fishtest/worker/updater.py", line 32, in update
    zip_file = ZipFile(worker_zip)
  File "/usr/lib64/python2.6/zipfile.py", line 696, in __init__
    self._GetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 716, in _GetContents
    self._RealGetContents()
  File "/usr/lib64/python2.6/zipfile.py", line 728, in _RealGetContents
    raise BadZipfile, "File is not a zip file"
BadZipfile: File is not a zip file

The script worker.py contains the line

WORKER_VERSION = 12

Current master is worker version 13 - https://github.com/glinscott/fishtest/b ... /worker.py - I think somehow you still have an old copy?

[Michel]

Ok it is solved.

I had done

rm -rf fishtest
git clone ...

BUT: the previous worker was still running in the background. So
rm -rf fishtest did not actually completely delete the directory fishtest. So the result of git clone was poisoned.

[gladius]

Ok it is solved.

I had done

rm -rf fishtest
git clone ...

BUT: the previous worker was still running in the background. So
rm -rf fishtest did not actually completely delete the directory fishtest. So the result of git clone was poisoned.

Ok, great! Glad it's working. Sorry for the updater problem, it should be rock solid from now on.

[Don]

Ok it is solved.

I had done

rm -rf fishtest
git clone ...

BUT: the previous worker was still running in the background. So
rm -rf fishtest did not actually completely delete the directory fishtest. So the result of git clone was poisoned.

Ok, great! Glad it's working. Sorry for the updater problem, it should be rock solid from now on.

Don't you guys have your own forum for communicating changes and dealing with administrative issues?

[ilari]

I'm late to the discussion as usual, but I have to congratulate the Stockfish team on their efforts and the inevitable success of the new testing framework. The technology may not be groundbreaking, but they've done many things extremely well. In just a couple of weeks I've seen many good patches come through, more and more people and machines are joining the project (today I saw 73 cores at work concurrently), the queue of pending tests is always populated, and the testing methodology is obviously getting better - proper stopping rules, varying time controls, testing uncertain patches both individually and as larger groups, regular regression tests, etc.

There's always going to be room for improvement but I don't think anyone can deny that Stockfish is getting stronger, and it's happening a lot faster than it used to happen.

[gladius]

Don't you guys have your own forum for communicating changes and dealing with administrative issues?

Yes! https://groups.google.com/forum/?fromgr ... ishcooking (the board seems to not like the ! in the url unfortunately) You reminded me we didn't have any links to the forum from the website - now corrected.

[gladius]

I'm late to the discussion as usual, but I have to congratulate the Stockfish team on their efforts and the inevitable success of the new testing framework. The technology may not be groundbreaking, but they've done many things extremely well. In just a couple of weeks I've seen many good patches come through, more and more people and machines are joining the project (today I saw 73 cores at work concurrently), the queue of pending tests is always populated, and the testing methodology is obviously getting better - proper stopping rules, varying time controls, testing uncertain patches both individually and as larger groups, regular regression tests, etc.

There's always going to be room for improvement but I don't think anyone can deny that Stockfish is getting stronger, and it's happening a lot faster than it used to happen.

Thank you Ilari! This would not exist without cutechess, and all your hard work on it.