From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] gnome-secrets: update to 7.0; New package: python3-zxcvbn-4.4.28
Date: Mon, 21 Nov 2022 03:15:56 +0100 [thread overview]
Message-ID: <20221121021556.Yudu0HV9d-ItnqvoCnYPKGCLjgCyVVF89SyXJ9A6BcU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40636@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
New review comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/40636#discussion_r1027449398
Comment:
```
=> python3-construct-2.10.68_1: running do_check ...
============================= test session starts ==============================
platform linux -- Python 3.11.0, pytest-7.1.3, pluggy-1.0.0
rootdir: /builddir/python3-construct-2.10.68
collected 0 items
============================ no tests ran in 0.01s =============================
=> ERROR: python3-construct-2.10.68_1: do_check: 'PYTHONPATH="$(cd build/lib* && pwd)" ${make_check_pre} python3 -m pytest ${testjobs} ${make_check_args} ${make_check_target}' exited with 5
=> ERROR: in do_check() at common/build-style/python3-module.sh:15
```
Maybe there just aren't any tests?
next prev parent reply other threads:[~2022-11-21 2:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 4:43 [PR PATCH] " cinerea0
2022-11-20 4:51 ` cinerea0
2022-11-20 5:14 ` [PR REVIEW] " classabbyamp
2022-11-20 20:50 ` [PR PATCH] [Updated] " cinerea0
2022-11-20 20:52 ` [PR REVIEW] " cinerea0
2022-11-20 20:52 ` cinerea0
2022-11-20 20:54 ` classabbyamp
2022-11-21 2:15 ` cinerea0 [this message]
2022-11-21 2:27 ` classabbyamp
2022-11-21 2:27 ` classabbyamp
2022-11-22 0:17 ` [PR PATCH] [Updated] " cinerea0
2022-11-22 0:21 ` [PR REVIEW] " cinerea0
2022-11-22 0:51 ` classabbyamp
2022-11-22 21:38 ` paper42
2022-11-23 5:22 ` [PR PATCH] [Updated] " cinerea0
2022-11-23 16:42 ` cinerea0
2022-11-24 7:28 ` [PR PATCH] [Merged]: " classabbyamp
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=20221121021556.Yudu0HV9d-ItnqvoCnYPKGCLjgCyVVF89SyXJ9A6BcU@z \
--to=cinerea0@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).