From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Coping with errors in starting async compilations Date: Mon, 18 Oct 2021 15:38:11 +0300 Message-ID: <83tuheecek.fsf@gnu.org> References: <83ilxvfnpq.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5343"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 18 14:43:41 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcRzQ-0001H6-Tj for ged-emacs-devel@m.gmane-mx.org; Mon, 18 Oct 2021 14:43:40 +0200 Original-Received: from localhost ([::1]:58446 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mcRzO-0007fs-UO for ged-emacs-devel@m.gmane-mx.org; Mon, 18 Oct 2021 08:43:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33964) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mcRu7-0001yh-L0 for emacs-devel@gnu.org; Mon, 18 Oct 2021 08:38:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37294) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mcRu2-0006SL-MX; Mon, 18 Oct 2021 08:38:11 -0400 Original-Received: from [87.69.77.57] (port=4666 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mcRu0-0002RO-Lx; Mon, 18 Oct 2021 08:38:05 -0400 In-Reply-To: (message from Andrea Corallo on Mon, 18 Oct 2021 08:44:41 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:277274 Archived-At: > From: Andrea Corallo > Cc: emacs-devel@gnu.org > Date: Mon, 18 Oct 2021 08:44:41 +0000 > > > 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. > > Hi Eli, > > good point, this is not handled. What should the intended behaivour we > want? Restart new compilations failed with EAGAIN and wait to start new > one? Yes, just like you do when the number of running jobs reaches the maximum allowed number: queue the rest for later execution. IOW, effectively behave like comp-effective-async-max-jobs was lowered.