From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Laurence Warne <laurencewarne@gmail.com>
Cc: contovob@tcd.ie, Eli Zaretskii <eliz@gnu.org>, 63550@debbugs.gnu.org
Subject: bug#63550: proced-refine-with-update-test is racy
Date: Wed, 24 May 2023 09:56:22 +0200 [thread overview]
Message-ID: <0DD23BEF-CC0C-4444-A175-FDC5FEF92C3B@gmail.com> (raw)
In-Reply-To: <CAE2oLqiVzn_+Efj-yUZf959VZezXO2wjmaurrRcUvFYZ17p_xw@mail.gmail.com>
21 maj 2023 kl. 20.45 skrev Laurence Warne <laurencewarne@gmail.com>:
> One thing I've noticed about the failing test is that we should probably use `(proced-update)` instead of `(proced-update t)` so as not to refresh `proced-process-alist` (I've attached a patch). When I first saw this, I thought this would fix the failure as I thought what might have been happening was that the process used for the refinement might have exited between proced being called, and then `(proced-update t)` being called, but I think the test should still pass in this case (though I've optimistically used 'fix' in the patch commit (: ).
These steps seem to provoke a failure of the original test quite reliably on macOS:
1. add the call (sleep-for 1) both before and after (proced-refine), to widen the windows
2. in a different terminal, keep the command
while true; do /bin/sleep 2 & sleep 0.1; done
running during the test, to create some churn in the process tables. (I'm using zsh if it matters.)
Changing (proced-update t) to (proced-update) does appear to remove the failure. Maybe you can decide whether it is better or not.
next prev parent reply other threads:[~2023-05-24 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 9:38 bug#63550: proced-refine-with-update-test is racy Mattias Engdegård
2023-05-17 11:44 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 8:37 ` Laurence Warne
2023-05-21 11:20 ` Eli Zaretskii
2023-05-21 18:45 ` Laurence Warne
2023-05-24 7:56 ` Mattias Engdegård [this message]
2023-05-27 19:14 ` Laurence Warne
2023-05-28 11:39 ` Mattias Engdegård
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=0DD23BEF-CC0C-4444-A175-FDC5FEF92C3B@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=63550@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=laurencewarne@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.