From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "John Soo" <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: RFC: subcommand to pause/resume builds
Date: Fri, 06 Nov 2020 16:11:54 -0500 [thread overview]
Message-ID: <87d00qb362.fsf@netris.org> (raw)
In-Reply-To: <87zh3yczss.fsf@gnu.org>
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> Last, you’d need to send SIGTSTP to the whole process group of the
> build, like so (I think, haven’t tried):
>
> sudo kill -TSTP -123
>
> where 123 is the “SessionPID” shown by ‘guix processes’. However, doing
> so may affect build results: processes in the build environment might
> handle SIGTSTP specially, which can have side effects. It’s an
> observable action.
What's the rationale for using SIGTSTP instead of SIGSTOP here?
FWIW, on a few occasions I've paused builds by sending SIGSTOP to the
relevant process group, and later SIGCONT, and it has worked for me. As
I recall, I've done this while building rust, webkitgtk, and icecat.
However, I suspect that if I paused a build while running tests, the
test suite might ultimately fail due to a "timeout".
> Conclusion: I don’t think we can implement this reliably.
Agreed.
Thanks,
Mark
next prev parent reply other threads:[~2020-11-06 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:56 RFC: subcommand to pause/resume builds John Soo
2020-11-03 13:53 ` Ludovic Courtès
2020-11-03 14:41 ` John Soo
2020-11-03 16:32 ` Tobias Geerinckx-Rice
2020-11-03 17:12 ` John Soo
2020-11-06 8:56 ` Ludovic Courtès
2020-11-03 17:19 ` Tobias Geerinckx-Rice
2020-11-03 18:27 ` John Soo
2020-11-03 20:01 ` John Soo
2020-11-06 8:58 ` Ludovic Courtès
2020-11-06 23:00 ` John Soo
2020-11-04 10:28 ` Bengt Richter
2020-11-06 21:11 ` Mark H Weaver [this message]
2020-11-08 16:30 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2020-11-05 4:37 John Soo
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d00qb362.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).