You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if you could control what build options the test is allowed to run with. There are cases where a patch only affects a specific build, take official-stockfish/Stockfish#3429 for example.
By default set the build to "unspecified" - whatever goes. Otherwise, if the worker machine doesn't support one of the required architectures it would be disqualified from running the test.
I suppose there are multiple ways of determining what build options are available:
Parsing the makefile
Including build options metadata with stockfish source, maybe a json file? Well some easy-to-parse configuration.
Coding the available options into fishtest (quite nasty imo)
I think a dedicated configuration file would be the best option, even though it could introduce discrepancies with the makefile. This should be controlled with Stockfish PRs though to remind people to update the fishtest configuation if they change the build parameters in the makefile.
The text was updated successfully, but these errors were encountered:
It would be great if you could control what build options the test is allowed to run with. There are cases where a patch only affects a specific build, take official-stockfish/Stockfish#3429 for example.
By default set the build to "unspecified" - whatever goes. Otherwise, if the worker machine doesn't support one of the required architectures it would be disqualified from running the test.
I suppose there are multiple ways of determining what build options are available:
I think a dedicated configuration file would be the best option, even though it could introduce discrepancies with the makefile. This should be controlled with Stockfish PRs though to remind people to update the fishtest configuation if they change the build parameters in the makefile.
The text was updated successfully, but these errors were encountered: