unofficial mirror of bug-gnu-emacs@gnu.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: gitmux@mail.stemux.com
Cc: 57301@debbugs.gnu.org
Subject: bug#57301: 28.1; 12 unexpected test results on emacs 28.1
Date: Sat, 20 Aug 2022 15:37:50 +0300	[thread overview]
Message-ID: <87wnb3ay5d.fsf@tcd.ie> (raw)
In-Reply-To: <87bksg2z0r.fsf@Mux.stemux.com> (gitmux@mail.stemux.com's message of "Fri, 19 Aug 2022 07:33:56 -0500")

gitmux@mail.stemux.com [2022-08-19 07:33 -0500] wrote:

> Running 7 tests (2022-08-19 06:35:19-0500, selector `(not (or (tag :expensive-test) (tag :unstable) (tag :nativecomp)))')
>   skipped  1/7  emacs-tests/bwrap/allows-stdout (0.000239 sec)
>    passed  2/7  emacs-tests/seccomp/absent-file (0.026424 sec)
> Test emacs-tests/seccomp/allows-stdout backtrace:
>   signal(ert-test-failed (((should (eql status 0)) :form (eql "Bad sys
>   ert-fail(((should (eql status 0)) :form (eql "Bad system call" 0) :v
>   #f(compiled-function () #<bytecode -0xfefa61c58ebb889>)()
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name emacs-tests/seccomp/allows-stdout :do
>   ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ... ...))
>   ert-run-tests((not (or (tag :expensive-test) (tag :unstable) (tag :n
>   ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable) (
>   ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
>   eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
>   command-line-1(("-L" ":." "-l" "ert" "-l" "src/emacs-tests" "--eval"
>   command-line()
>   normal-top-level()
> Test emacs-tests/seccomp/allows-stdout condition:
>     Info: Process output:
>           
>     (ert-test-failed
>      ((should
>        (eql status 0))
>       :form
>       (eql "Bad system call" 0)
>       :value nil))
>    FAILED  3/7  emacs-tests/seccomp/allows-stdout (0.026337 sec)
>    passed  4/7  emacs-tests/seccomp/empty-file (0.018653 sec)
>    passed  5/7  emacs-tests/seccomp/file-too-large (0.043209 sec)
>    passed  6/7  emacs-tests/seccomp/forbids-subprocess (0.020086 sec)
>    passed  7/7  emacs-tests/seccomp/invalid-file-size (0.019868 sec)
>
> Ran 7 tests, 5 results as expected, 1 unexpected, 1 skipped (2022-08-19 06:35:20-0500, 0.239446 sec)
>
> 1 unexpected results:
>    FAILED  emacs-tests/seccomp/allows-stdout
>
> 1 skipped results:
>   SKIPPED  emacs-tests/bwrap/allows-stdout

This could be https://bugs.gnu.org/51073
or https://bugs.gnu.org/56359.

-- 
Basil





      parent reply	other threads:[~2022-08-20 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 12:33 bug#57301: 28.1; 12 unexpected test results on emacs 28.1 gitmux
2022-08-19 18:14 ` Stefan Kangas
2022-08-20 13:17   ` gitmux
2022-08-21 12:21     ` Lars Ingebrigtsen
2022-08-22 22:49       ` archmux
2022-08-23 10:37         ` Lars Ingebrigtsen
2022-08-23 14:32           ` Robert Pluim
2022-08-24 22:49             ` archmux
2022-08-25  8:04               ` Robert Pluim
2022-08-20 12:37 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87wnb3ay5d.fsf@tcd.ie \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57301@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=gitmux@mail.stemux.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).