Coping with errors in starting async compilations

[Eli Zaretskii]

Andrea,

Is comp-run-async-workers capable of coping with failures to launch a
sub-process due to stuff like insufficient resources?  For example,
Emacs on MS-Windows doesn't allow to start more than 31 sub-processes
(including network connections, so it could be less than that), so
what happens when comp-run-async-workers attempts to start another
sub-process and that fails with EAGAIN?  That should be handled like
reaching the limitation of comp-effective-async-max-jobs.  Perhaps it
already is?

Thanks.