unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "J.P." <jp@neverwas.me>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-erc@gnu.org, 72004@debbugs.gnu.org
Subject: bug#72004: 30.0.50, master: 'erc--check-prompt-input-for-multiline-blanks' test fail
Date: Thu, 11 Jul 2024 11:26:15 -0700	[thread overview]
Message-ID: <87bk33ss3c.fsf__8508.81557432643$1720722451$gmane$org@neverwas.me> (raw)
In-Reply-To: <yp1r0c0cp4i.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Thu, 11 Jul 2024 04:24:45 -0400")

Andrea Corallo <acorallo@gnu.org> writes:

> I buy the theory of this being related to trampoline generation under
> high system load, looking at my logs I see this test failing only with
> native compilation an passing without.
>
> I'm wondering if we could work around the issue somehow 🤔

I'm afraid I can offer next to nothing when it comes to serious insights
about Emacs internals and related magic 😞

>
> Also I'm not sure the right tag is :expensive, shouldn't be :unstable?

If we want to prevent the test from running completely (at least on
EMBA), then :unstable would indeed make sense. However, if we'd like the
test to run on the 3x daily expensive pipelines, I'm fairly confident my
latest change sidesteps the issue. It now waits to start the subprocess,
which was previously too short-lived, until after the macro has done its
(potentially time-consuming) advising. Thus, the liveliness check that
was signaling the error should now always find a running process.
(Although, for good measure, I also lengthened the timeout from 10s to
5m.) All this said, I'm happy to change it to :unstable or try a safer
approach, such as mocking `process-status'. Thanks.





  reply	other threads:[~2024-07-11 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  8:08 bug#72004: 30.0.50, master: 'erc--check-prompt-input-for-multiline-blanks' test fail Andrea Corallo
2024-07-09 11:41 ` Eli Zaretskii
2024-07-11  7:10   ` J.P.
     [not found]   ` <87cynkv1yf.fsf@neverwas.me>
2024-07-11  8:24     ` Andrea Corallo
2024-07-11 18:26       ` J.P. [this message]
     [not found]       ` <87bk33ss3c.fsf@neverwas.me>
2024-07-12  7:30         ` Andrea Corallo

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87bk33ss3c.fsf__8508.81557432643$1720722451$gmane$org@neverwas.me' \
    --to=jp@neverwas.me \
    --cc=72004@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-erc@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/emacs.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).