Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

Dan, > On Jun 18, 2024, at 09:44, Dan Shelton via Cygwin wrote: > > On Mon, 17 Jun 2024 at 18:03, Dale Lobb (Sys Admin) via Cygwin > wrote: >> >> Greetings, Nicholas; >> >>> From: Cygwin On >>> Behalf Of Andrey Repin via Cygwin >>> Sent: Monday, June 17, 2024 2:58 AM >>> To: Nicholas Willia

Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

Andrey and Dale, > On Jun 17, 2024, at 11:03, Dale Lobb (Sys Admin) > wrote: > > Greetings, Nicholas; > >> From: Cygwin > > On Behalf Of >> Andrey Repin via Cygwin >> Sent: Monday, June 17, 2024 2:58 AM >> To: Nicholas Williams >

Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

Hello, We have a Python (installed and run through Cygwin) process running on Windows Server 2022 that was very, very occasionally failing when subprocess.check_output was called: 0 [main] python3 28481 dofork: child -1 - forked process 16856 died unexpectedly, retry 0, exit code 0xC142, e