From: Roman Scherer <roman@burningswell.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: Roman Scherer <roman@burningswell.com>, 74728@debbugs.gnu.org
Subject: [bug#74728] [PATCH] gnu: python-asyncssh: Disable more tests.
Date: Sun, 08 Dec 2024 18:32:50 +0100 [thread overview]
Message-ID: <86jzcaw059.fsf@burningswell.com> (raw)
In-Reply-To: <CAO+9K5qHNTMVTZjcP6_pu7krmhzyWHL7gjoQaYONbo5rPQbHjQ@mail.gmail.com> (Sharlatan Hellseher's message of "Sun, 8 Dec 2024 16:43:39 +0000")
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
Sharlatan Hellseher <sharlatanus@gmail.com> writes:
Hi Oleg,
yes, maybe better. I sent a version of the previous patch that only
disables those tests on aarch64.
Wdyt?
Thanks, Roman.
> Hi,
>
> CI for x86_64 just finished without issues, note I've refunded the
>
> version.
>
> Maybe we may make flakey test architecture specific, WDYT?
>
> Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
next prev parent reply other threads:[~2024-12-08 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 18:00 [bug#74728] [PATCH] gnu: python-asyncssh: Disable flaky connection tests Roman Scherer
2024-12-07 22:40 ` Sharlatan Hellseher
2024-12-08 12:33 ` bug#74728: " Sharlatan Hellseher
2024-12-08 14:15 ` [bug#74728] [PATCH] gnu: python-asyncssh: Disable more tests Roman Scherer
2024-12-08 16:43 ` Sharlatan Hellseher
2024-12-08 17:32 ` Roman Scherer [this message]
[not found] ` <handler.74728.D74728.173366126726317.notifdone@debbugs.gnu.org>
2024-12-08 14:18 ` [bug#74728] closed ([PATCH] gnu: python-asyncssh: Disable flaky connection tests.) Roman Scherer
2024-12-08 17:31 ` [bug#74728] [PATCH] gnu: python-asyncssh: Disable failing tests on aarch64 Roman Scherer
2024-12-09 21:27 ` [bug#74728] [PATCH] gnu: python-asyncssh: Disable flaky connection tests Sharlatan Hellseher
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=86jzcaw059.fsf@burningswell.com \
--to=roman@burningswell.com \
--cc=74728@debbugs.gnu.org \
--cc=sharlatanus@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 external index
https://git.savannah.gnu.org/cgit/guix.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.