From: Eli Zaretskii <eliz@gnu.org>
To: Laurence Warne <laurencewarne@gmail.com>
Cc: contovob@tcd.ie, mattias.engdegard@gmail.com, 63550@debbugs.gnu.org
Subject: bug#63550: proced-refine-with-update-test is racy
Date: Sun, 21 May 2023 14:20:06 +0300 [thread overview]
Message-ID: <83pm6uq6c9.fsf@gnu.org> (raw)
In-Reply-To: <CAE2oLqhYoFeZbyGUjjMpMk5ZF+gfG6bu_30y1yPNYvbqHR-25A@mail.gmail.com> (message from Laurence Warne on Sun, 21 May 2023 09:37:10 +0100)
> Cc: Mattias Engdegård <mattias.engdegard@gmail.com>,
> 63550@debbugs.gnu.org
> From: Laurence Warne <laurencewarne@gmail.com>
> Date: Sun, 21 May 2023 09:37:10 +0100
>
> Strange, I can't seem to reproduce running it continuously (I'm on linux also). Though whilst looking
> over the test suite, I don't think I like the approach I took. I've attached a new patch which changes the
> test suite to mock the list of active processes (of course comments welcome).
>
> Are either of you able to test whether this fixes the test in question? The change also makes the tests
> a lot faster to run and hopefully less system dependent.
Is mocking out the real Proced display a good idea in this case?
These tests test the ability to manipulate real-life process-attribute
displays, so showing they work in synthetic environment verifies only
part of the functionality, no?
next prev parent reply other threads:[~2023-05-21 11:20 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 [this message]
2023-05-21 18:45 ` Laurence Warne
2023-05-24 7:56 ` Mattias Engdegård
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=83pm6uq6c9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63550@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=laurencewarne@gmail.com \
--cc=mattias.engdegard@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.