From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-ipyparallel: enable check
Date: Mon, 25 Sep 2023 03:43:33 +0200 [thread overview]
Message-ID: <20230925014333.hFoCdWEFeW6IBGdLw8PfnqRSVg1zVqp-etvRscxcAE0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46209@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/46209#issuecomment-1732777518
Comment:
@ahesford I had to disable check on musl since it's broken, both in CI and locally. The cluster just gets stuck (it seems a python process dies but the parent doesn't realize).
The checks pass just fine in x86_64 and i686 (both locally and in all my pushes to gh), so this is better than what was there before.
I'm not looking into it anymore. As a starting point, `ipyparallel/tests/test_apps.py::test_ipcluster_start_stop` always fails. But then other files sometimes result in all errors (not failures), sometimes they don't (test_asyncresult.py, test_client.py, test_cluster.py, ...).
next prev parent reply other threads:[~2023-09-25 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46209@inbox.vuxu.org>
2023-09-24 23:09 ` [PR PATCH] [Updated] " tornaria
2023-09-24 23:23 ` tornaria
2023-09-25 1:30 ` tornaria
2023-09-25 1:43 ` tornaria [this message]
2023-09-25 1:57 ` [PR REVIEW] " ahesford
2023-09-25 1:57 ` ahesford
2023-09-25 23:19 ` [PR PATCH] [Updated] " tornaria
2023-09-26 1:21 ` [PR PATCH] [Merged]: " ahesford
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=20230925014333.hFoCdWEFeW6IBGdLw8PfnqRSVg1zVqp-etvRscxcAE0@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).