On Tue, 29 Jul 2025, Cedric Blancher via Cygwin wrote: > Good moring! > > Could the posix_spawn() work (branch heads/topic/posix_spawn) be > merged now, but the new version kept off by default unless an option > in the CYGWIN env var is set? > > That would make testing IMO much easier...
It could be, but I don't see how that would help much. Based on previous bugs that made it through to release, I am not sure that the snapshot builds get all that much exercise in the first place. Also requiring setting an environment variable to enable the code path would reduce the exposure even more, to the point that I doubt anyone would use it. I use the artifact generated by GitHub Actions to test, and I also backport on top of 3.6 for testing so I have a 3.6.3 with the posix_spawn patches which I use to build llvm & clang weekly and rust nightly in GitHub Actions. Would it be helpful for me to send a new version of the patch series to the list for review? I did update the child_info_spawn::worker args (mode, prog_arg, and the rest in a const struct reference) and update to use a local child_info_spawn instance like system and popen now do since the last version I sent.