vdbergh
vdbergh
Allowing the clone workers to update would lead to pretty bad race conditions. So I adapted the proposal accordingly.
> to stop or restart only 1-2 workers without stopping or restating all the workers, so losing the games played I was thinking that from the point of view of...
We can set the default value of pool to ceil(concurrency/32). In that way nothing would change for workers with
It could be due to the test setting an option that does not exist. Then the worker will stop the test. However I guess there should be some audit trail...
It seems `run["failed"]=True` can only be set by invoking the api `api_stop_run`. But in that case there should be a message in `actiondb`.
Hmmm. This raises more questions :frowning_face: . Why is the message there twice? And why did it happen after the run was finished? EDIT. The two message are wide apart...
The last update for this test was received `2021-10-09 18:44:28`. So this does not correspond to the two action messages....
I did not know that it is possible to restart a finished test. EDIT: I looked at the code for `tests_modify`. It seems it can create runs with `run["finished"]=False` which...
No this is not possible since `run["failed"]=True` can only set by `api_stop_run`. Mystery.
> The last update for this test was received `2021-10-09 18:44:28`. So this does not correspond to the two action messages... I deleted the previous post since the explanation is...