dgrnbrg/autotest — comment on commit cd4da65bb0f7cdad505bd1f97ca18ba6e1f5e6ee
File: server/hosts/logfile_monitor.py line 90
By jzupka:

Yes, I agree that potential problem should be weighed against the benefit.
There is low probability to get to line with host.job.record in this case and
there is no multi indentation status writes by this record.
I made some test with multithreaded writing to status file by 100 parallel threads
using host.job.record and there is no mishmash in status file only some missing line
in stdout result. Writing to status file should be treated by file locking in
base_job.py->class status_logger->function record_entry and some other changes.
Bigger problem is in the file serve_job.py->class server_job_record_hook->__call__.
There is lock which block writing from multiple threads at some time.
If there will be an effort made more things parallel, we should review the loging.