From: Lars Ingebrigtsen <larsi@gnus.org>
To: p.stephani2@gmail.com
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
56359@debbugs.gnu.org, Glenn Morris <rgm@gnu.org>
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Fri, 07 Oct 2022 13:56:32 +0200 [thread overview]
Message-ID: <87wn9bvocv.fsf@gnus.org> (raw)
In-Reply-To: <87wn9cvqkq.fsf@tcd.ie> (Basil L. Contovounesios's message of "Thu, 06 Oct 2022 19:56:21 +0300")
"Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army
knife of text editors" <bug-gnu-emacs@gnu.org> writes:
> 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?
They've certainly been problematic, so perhaps that's the best solution
as this point. Perhaps it would be possible to avoid marking them as
unstable on platforms they're known to be working (and should continue
working)? I'm not at all sure how to get as such a list, though.
prev parent reply other threads:[~2022-10-07 11: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
2022-10-07 11:56 ` Lars Ingebrigtsen [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=87wn9bvocv.fsf@gnus.org \
--to=larsi@gnus.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 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).