From: Roumen Petrov <bugtrack@roumenpetrov.info>
To: cygwin@cygwin.com
Subject: OS hang when multi-process build fail
Date: Sat, 4 Dec 2021 10:51:14 +0200 [thread overview]
Message-ID: <577e34bb-9e73-928c-9cf7-a448ec3e5d32@roumenpetrov.info> (raw)
Hello Cygwin users,
On non regular basis I would like to perform regression test of recent pkix-ssh version with recent openssl release.
In this case is was openssl master branch now release as 3.0.
The problem is that with current cygwin packages gcc make and etc. openssl build with "num of cpu + 1" processes fail with communication error.
Issue is that in such case operation system is unusable. It respond on mouse events but build process in cygwin console cannot be canceled by keyboard interrupt signal (crtl+c). Also cygwin console window cannot be closed as well. More over "task manager" and etc cannot be started and I must shutdown OS - [power] button works.
Builds were run in cygwin console without administrative rights.
It seems to me current cygwin release has issue with inter-process communication, for instance in setup program as well.
Regards,
Roumen Petrov
P.S. Now I use single process "night"-build as work-around.
next reply other threads:[~2021-12-04 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 8:51 Roumen Petrov [this message]
2021-12-04 10:34 ` Marco Atzeri
2021-12-06 18:13 ` Roumen Petrov
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=577e34bb-9e73-928c-9cf7-a448ec3e5d32@roumenpetrov.info \
--to=bugtrack@roumenpetrov.info \
--cc=cygwin@cygwin.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).