all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Laurence Warne <laurencewarne@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: mattiase@acm.org, 73441@debbugs.gnu.org, Sam James <sam@gentoo.org>
Subject: bug#73441: 31.0.50; Unstable proced-refine-test failure
Date: Sat, 9 Nov 2024 21:18:11 +0000	[thread overview]
Message-ID: <CAE2oLqhXuUcyie=WX2e2O_XUtwWhh_qThZ_ftV6osWhAHKWdKg@mail.gmail.com> (raw)
In-Reply-To: <87msi8894l.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

> Yes, checking for -nan seems to be the best choice we have. So we must
> replace (thing-at-point 'number) with something else in
proced-refine-test,
> proced-refine-with-update-test,
proced--assert-process-valid-cpu-refinement
> and proced--assert-process-valid-cpu-refinement-explainer. Would you
> like to provide a patch?

I was thinking more along the lines of a 'isnan' check in 'proced-<' to the
effect of making it not appear in any refinements at all, but if you think
it's too much fretting about an edge case, I'm happy to provide a patch for
the tests only (as you describe)?

> (see sysdep.c). If one of the operands is not proper, the result can be
> a NaN indeed, like -0.0e+NaN.

Could you explain what is meant by proper?

[-- Attachment #2: Type: text/html, Size: 1103 bytes --]

  reply	other threads:[~2024-11-09 21:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 13:19 bug#73441: 31.0.50; Unstable proced-refine-test failure Sam James
2024-09-27 13:00 ` Laurence Warne
2024-10-15 14:52   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25 16:46     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 15:44       ` Laurence Warne
2024-10-26 16:59         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 11:16           ` Laurence Warne
2024-10-27 11:47             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 12:07               ` Eli Zaretskii
2024-10-27 15:53                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29  7:51         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29 21:26           ` Laurence Warne
2024-10-30 14:15             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 18:25               ` Laurence Warne
2024-11-04 13:27                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09  8:31                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 14:17                     ` Laurence Warne
2024-11-09 20:06                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 21:18                         ` Laurence Warne [this message]
2024-11-10  8:35                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-12 20:19                             ` Laurence Warne
2024-11-13  8:04                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 18:24                                 ` Laurence Warne
2024-11-15 15:25                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CAE2oLqhXuUcyie=WX2e2O_XUtwWhh_qThZ_ftV6osWhAHKWdKg@mail.gmail.com' \
    --to=laurencewarne@gmail.com \
    --cc=73441@debbugs.gnu.org \
    --cc=mattiase@acm.org \
    --cc=michael.albinus@gmx.de \
    --cc=sam@gentoo.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 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.