ppigazzini
ppigazzini
DEV updated after https://github.com/glinscott/fishtest/pull/1379/commits/552517d661d4541b3ad3f4e7084b665916c9f4f1
According a SF dev this is a long time behavior, not a bug introduced with last PRs.
I'm wondering where you have read "won't fix"...
The chi2 code aggregates the results by worker, so theoretically changing the batch size could change the number of unique workers in the test and change a little bit the...
Script for linux: - creates the "fishtest" user - creates 5 copies of the "worker" directory to be able to run 5 workers - creates an unit systemd file (name...
Problems: - the user willingness to start N workers, with or `--pool` or systemd. The big workers are contributed by people with high skillset, surely able to setup an unit...
> Okay, then I guess we should implement them into fishtest; otherwise we won't have the required resources to test them. More realistic is to find some easy tunable parameters,...
It should be this (I checked "Actions" before opening the issue... I obviously missed it ...): Time | Username | Run/User | Action -- | -- | -- | --...
> Hmmm. This raises more questions ☹️ . Why is the message there twice? And why did it happen after the run was finished? > > EDIT. The two message...
This is clear: - the worker with wrong bench called `api_stop_run`, this set `run["failed"]=True` - the developer restarted the run with the `modify` trick (`run["failed"]=True` is not cleared) - when...