From: "Christian Köstlin" <christian.koestlin@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Ignore flaky ob-python tests
Date: Wed, 2 Nov 2022 12:15:53 +0100 [thread overview]
Message-ID: <CAG741+ax-QKajUj0+JibwnK09NDuFX1AxKDUfxkB7hKAo=LLTw@mail.gmail.com> (raw)
In-Reply-To: <878rktluej.fsf@localhost>
On Wed, Nov 2, 2022 at 7:52 AM Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Christian Köstlin <christian.koestlin@gmail.com> writes:
>
> > The new async feature of python seems to be implemented in a way
> > that can break with high CPU load. This patch still runs the 3 tests in
> > question, but does not fail the complete testsuite if any of those fail.
>
> Thanks for the patch, but I'm afraid that it will drive the tests useless.
> After the patch, even if the tests fail for a valid reason, it will not
> be visible upon running make test, AFAIU.
I think we know of the async problem, and you reported that as well,
so I would expect
if someone is able to fix it, he will also move the tests to "sharp" again.
With my patch the tests are still failing but the testsuite continues
to run and returns
with 0 as status code (one can see the failed test though).
> Maybe we can instead provide some variable that can turn-on ignoring
> some problematic tests only during CI tests?
Yes ... that would also be possible e.g. skip the test or test nothing
if it's running on the ci.
(I am talking only about the 3 tests!).
Kind regards,
Christian
next prev parent reply other threads:[~2022-11-02 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 0:41 [PATCH] Ignore flaky ob-python tests Christian Köstlin
2022-11-02 6:53 ` Ihor Radchenko
2022-11-02 11:15 ` Christian Köstlin [this message]
2022-11-02 13:55 ` Jack Kamm
2022-11-02 14:12 ` Ihor Radchenko
2022-11-02 14:17 ` Ihor Radchenko
2022-11-03 7:14 ` Ihor Radchenko
2022-11-03 21:15 ` Christian Köstlin
2022-11-04 4:19 ` Ihor Radchenko
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='CAG741+ax-QKajUj0+JibwnK09NDuFX1AxKDUfxkB7hKAo=LLTw@mail.gmail.com' \
--to=christian.koestlin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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.