From: Luciogi <Luciogi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [tracking]: List of currently failing python3 checks
Date: Sat, 18 Nov 2023 05:26:33 +0100 [thread overview]
Message-ID: <20231118042633._NhCDyM75GdF1f0Jwt9yLifbg1DztsDW02NrbOR8yMo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46170@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
New comment by Luciogi on void-packages repository
https://github.com/void-linux/void-packages/issues/46170#issuecomment-1772944457
Comment:
Hi, Can I run tests locally ?
Edit: nvm got it `xbps-src check`
- [x] ranger
all tests are passing
- [x] virt-manager
fixed in #46885
test are passing on python3.11 (i saw on their github workflow logs)
on void I use python3.12 it fails , with difference of `http` -> 3.11 and `https`->3.12
issue is reported https://github.com/virt-manager/virt-manager/issues/595
- [x] **greg**
fixed in #46809
- [x] **tuimoji**
fixed in #46810
- [x] **wfuzz**
fixed in #46812
- [x] **bCNC**
fixed in #46817
- [x] **duplicity**
all tests are passing
- [x] **hg-git**
fixed in #46887
---
Unchecked
- [ ] cpuset
depends on python3-future, which uses `import imp` , `imp` is removed from python 3.12
- [x] **mate-menu**
fixed in #47193
- [x] **flowblade**
fixed in #47195
- [x] **reuse**
fixed in #47227
- [x] **python3-Markups**
fixed in #47283
- [x] **python3-SQLAlchemy2**
fixed in #47286 (test passing without any modification)
- [x] **python3-Cheroot**
fixed in #47289
- [x] **python3-SoCo**
fixed in #47292
next prev parent reply other threads:[~2023-11-18 4:26 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:18 [ISSUE] " paper42
2023-09-22 22:29 ` tornaria
2023-09-27 11:39 ` Requion
2023-10-20 15:22 ` Luciogi
2023-10-20 17:00 ` Luciogi
2023-10-20 17:09 ` Luciogi
2023-10-20 17:49 ` Luciogi
2023-10-20 17:50 ` Luciogi
2023-10-21 6:00 ` Luciogi
2023-10-21 6:02 ` Luciogi
2023-10-21 6:02 ` Luciogi
2023-10-21 6:41 ` Luciogi
2023-10-21 7:12 ` Luciogi
2023-10-25 9:13 ` Luciogi
2023-10-25 13:31 ` Luciogi
2023-10-25 13:34 ` Luciogi
2023-10-26 16:02 ` Luciogi
2023-11-13 12:48 ` Luciogi
2023-11-13 13:13 ` Luciogi
2023-11-13 13:15 ` Luciogi
2023-11-13 13:17 ` Luciogi
2023-11-13 13:25 ` Luciogi
2023-11-13 14:42 ` Luciogi
2023-11-14 6:51 ` Luciogi
2023-11-17 16:42 ` Luciogi
2023-11-17 18:43 ` Luciogi
2023-11-18 4:07 ` Luciogi
2023-11-18 4:26 ` Luciogi [this message]
2023-11-18 5:12 ` Luciogi
2023-11-18 5:32 ` Luciogi
2023-11-21 10:33 ` Luciogi
2023-11-23 6:23 ` Luciogi
2023-11-23 6:27 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:28 ` Luciogi
2023-11-23 6:29 ` Luciogi
2023-11-23 6:29 ` Luciogi
2023-11-23 6:29 ` Luciogi
2023-11-23 6:31 ` Luciogi
2023-11-23 6:31 ` Luciogi
2023-11-23 6:31 ` Luciogi
2023-11-23 6:32 ` Luciogi
2023-11-23 6:32 ` Luciogi
2023-11-23 6:32 ` Luciogi
2023-11-23 6:32 ` Luciogi
2023-11-23 6:32 ` Luciogi
2023-11-23 6:33 ` Luciogi
2023-11-23 6:33 ` Luciogi
2023-11-23 6:33 ` Luciogi
2023-11-23 7:27 ` Luciogi
2023-11-23 9:52 ` Luciogi
2023-11-23 9:52 ` Luciogi
2023-11-23 9:52 ` Luciogi
2023-11-23 9:52 ` Luciogi
2023-11-23 12:58 ` Luciogi
2023-11-23 12:59 ` Luciogi
2023-11-24 9:20 ` Luciogi
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=20231118042633._NhCDyM75GdF1f0Jwt9yLifbg1DztsDW02NrbOR8yMo@z \
--to=luciogi@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).