vdbergh
vdbergh
Currently blocked workers stay in the blocked worker list forever (unless you unblock them which is not _really_ what you want to do). So by default the list becomes longer...
I wonder if there is any appetite for auto blocking workers under some conditions. For example after two (three?) consecutive crash_or_time events.
Setting this to > 1 guarantees that you will almost never get any tasks. So you may as well not run a worker.
Note that pagination for the finished runs always worked well (in contrast to the event log). 
```sh woolf@pl2:~$ wget tests.stockfishchess.org/api/active_runs URL transformed to HTTPS due to an HSTS policy --2023-05-09 15:26:25-- https://tests.stockfishchess.org/api/active_runs Resolving tests.stockfishchess.org (tests.stockfishchess.org)... 185.83.217.134 Connecting to tests.stockfishchess.org (tests.stockfishchess.org)|185.83.217.134|:443... connected. HTTP request sent, awaiting response......
There is some literal code duplication between `application.js` and `test_view.mak`. E.g. `getPreferredTheme()`. I assume the code in `tests_view.mak` can be deleted?
We use the logger "fishtest" as configured in production.ini. For messages to the event log we use the child logger "fishtest.event", also configured in production.ini. Log messages are formatted as...
With this PR `/api/serialize_run` hosted by the main instance can be invoked by a secondary instance to receive a copy of the run from the cache. In this way there...
The main reason for this PR is that currently the residuals are updated in `tests_view`. This is *wrong*. `tests_view` is a GET request. It is not allowed to change the...
See https://tests.stockfishchess.org/actions?max_actions=1&action=log_message&user=&text=&before=1725836603.523324&run_id= Probably, in a future PR, we will delegate the purging of the "active_runs" data structure to a scheduled task so that there is no more need for the...