From: Bart Schaefer <schaefer@brasslantern.com> To: Philippe Troin <phil@fifi.org> Cc: Perry Smith <pedz@easesoftware.com>, Zsh Users <zsh-users@zsh.org> Subject: Re: Parallel processing Date: Sun, 27 Mar 2022 10:42:43 -0700 [thread overview] Message-ID: <CAH+w=7ZMXdnz2wq448D58y1Gs0Zw95v89c4ryzs2MkJ9=-HvcQ@mail.gmail.com> (raw) In-Reply-To: <b84b8855cc6c8f7e1d30ee37169b158c68188c93.camel@fifi.org> On Sun, Mar 27, 2022 at 10:32 AM Philippe Troin <phil@fifi.org> wrote: > > I was referring to the fact that zargs misses the exit status of > subcommands: Yes, I addressed that when I said >> However, that "wait" returns the exit status of only one of those jobs. > In the first invocation, zargs misses that one of the subshells returns > non-zero exit status. That's also mentioned in the comments in the source file: # With the --max-procs option, zargs may not correctly capture the exit # status of the backgrounded jobs, because of limitations of the "wait" # builtin. If the zsh/parameter module is not available, the status is # NEVER correctly returned, otherwise the status of the longest-running # job in each batch is captured. However, see patch submitted a few minutes ago to zsh-workers.
next prev parent reply other threads:[~2022-03-27 17:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-25 4:34 Perry Smith 2022-03-25 18:27 ` Bart Schaefer 2022-03-26 18:10 ` Philippe Troin 2022-03-26 22:19 ` Bart Schaefer 2022-03-27 17:32 ` Philippe Troin 2022-03-27 17:42 ` Bart Schaefer [this message] 2022-03-27 19:23 ` Dominik Vogt 2022-03-28 13:26 ` Perry Smith 2022-03-28 13:31 ` Perry Smith 2022-03-26 4:34 jdh 2022-03-27 18:37 jdh 2022-03-27 19:06 ` Bart Schaefer 2022-03-27 19:24 ` Ray Andrews 2022-03-28 13:47 ` Perry Smith
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAH+w=7ZMXdnz2wq448D58y1Gs0Zw95v89c4ryzs2MkJ9=-HvcQ@mail.gmail.com' \ --to=schaefer@brasslantern.com \ --cc=pedz@easesoftware.com \ --cc=phil@fifi.org \ --cc=zsh-users@zsh.org \ --subject='Re: Parallel processing' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.vuxu.org/mirror/zsh/ This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).