unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 46834@debbugs.gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#46834: 28.0.50; byte-compiling the standard counter closure fails
Date: Mon, 01 Mar 2021 18:31:30 +0200	[thread overview]
Message-ID: <83blc296ot.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBcp8zPsiBVaw5Tjkh7OxX-izsbi3i0OAzjbGRjcXE0BZg@mail.gmail.com> (message from Pip Cet on Mon, 1 Mar 2021 15:16:22 +0000)

> From: Pip Cet <pipcet@gmail.com>
> Date: Mon, 1 Mar 2021 15:16:22 +0000
> Cc: 46834@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
> 
> I've been meaning to ask, is there anything like an XFAIL test in our
> current framework?

Yes, see the node "Expected Failures" in the ert manual.





      parent reply	other threads:[~2021-03-01 16:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 15:04 bug#46834: 28.0.50; byte-compiling the standard counter closure fails Pip Cet
2021-02-28 19:57 ` Pip Cet
2021-02-28 20:34   ` Pip Cet
2021-03-01 14:23     ` Stefan Monnier
2021-03-01 15:01       ` Pip Cet
2021-03-01 16:02         ` Stefan Monnier
2021-03-02  7:00           ` Lars Ingebrigtsen
2021-03-02  7:31             ` Pip Cet
2021-03-02  7:34               ` Lars Ingebrigtsen
2021-03-02  7:36                 ` Pip Cet
2021-03-02 13:16                 ` Eli Zaretskii
2021-03-02 13:19                   ` Pip Cet
2021-03-02 13:48                     ` Eli Zaretskii
2021-03-01 13:16   ` Lars Ingebrigtsen
2021-03-01 14:34     ` Stefan Monnier
2021-03-01 15:16       ` Pip Cet
2021-03-01 16:15         ` Stefan Monnier
2021-03-01 16:41           ` Pip Cet
2021-03-01 17:01             ` Stefan Monnier
2021-03-01 17:13               ` Pip Cet
2021-03-01 16:31         ` Eli Zaretskii [this message]

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=83blc296ot.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46834@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pipcet@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 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).