all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: p.stephani2@gmail.com
Cc: 56359@debbugs.gnu.org, Glenn Morris <rgm@gnu.org>
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Thu, 06 Oct 2022 19:56:21 +0300	[thread overview]
Message-ID: <87wn9cvqkq.fsf@tcd.ie> (raw)
In-Reply-To: <mk8rpbv26z.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 02 Jul 2022 13:45:08 -0400")

found 56359 28.2.50
found 56359 29.0.50
quit

Glenn Morris [2022-07-02 13:45 -0400] wrote:

> emacs-28 at e390396e684 on RHEL 9.0:
>
> 2 unexpected results:
>    FAILED  emacs-tests/bwrap/allows-stdout
>    FAILED  emacs-tests/seccomp/allows-stdout

I'm still seeing these failures.  Considering their history (bug#47708,
bug#47828, bug#51073, bug#53504, bug#57301), perhaps these tests should
be tagged as :unstable?

Thanks,

-- 
Basil





  parent reply	other threads:[~2022-10-06 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 17:45 bug#56359: seccomp test failures on RHEL 9.0 Glenn Morris
2022-07-15 14:12 ` Philipp Stephani
2022-07-15 23:35   ` Glenn Morris
2022-07-16 10:50     ` Philipp Stephani
2022-08-20 12:37       ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11  0:54         ` Lars Ingebrigtsen
2022-10-11 12:36           ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11 17:43             ` Paul Eggert
2022-10-11 19:47               ` Lars Ingebrigtsen
2022-10-18  9:32                 ` Philipp Stephani
2022-10-06 16:56 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-07 11:56   ` Lars Ingebrigtsen

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=87wn9cvqkq.fsf@tcd.ie \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56359@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=p.stephani2@gmail.com \
    --cc=rgm@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 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.