Github messages for voidlinux
 help / color / mirror / Atom feed
From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] puddletag: update to 2.1.1.
Date: Sun, 13 Feb 2022 12:05:52 +0100	[thread overview]
Message-ID: <20220213110552.TagJ0RYmDai61RhNEJY7kgH9iw4qYJp6j8lDexpwVJ0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35562@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/35562#discussion_r805317503

Comment:
I'm not that familiar with python tests but our python3-module build-style indicates that there are two ways of testing. One with pytest and the other one with setup.py which is deprecated. Seems like this one doesn't make use of pytest but uses the deprecated one which runs when I remove the python3-pytest dependency. Then it shows 51 failed tests. I force pushed now so you can see the logs.

  parent reply	other threads:[~2022-02-13 11:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 20:48 [PR PATCH] " tibequadorian
2022-02-12 21:01 ` [PR PATCH] [Updated] " tibequadorian
2022-02-12 21:06 ` tibequadorian
2022-02-12 21:31 ` tibequadorian
2022-02-12 21:36 ` tibequadorian
2022-02-12 22:46 ` [PR REVIEW] " paper42
2022-02-13  0:03 ` tibequadorian
2022-02-13  0:24 ` [PR PATCH] [Updated] " tibequadorian
2022-02-13  0:30 ` [PR REVIEW] " tibequadorian
2022-02-13  0:30 ` tibequadorian
2022-02-13 10:43 ` UsernameRandomlyGenerated
2022-02-13 11:05 ` [PR PATCH] [Updated] " tibequadorian
2022-02-13 11:05 ` tibequadorian [this message]
2022-06-23  2:16 ` github-actions
2022-07-08  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20220213110552.TagJ0RYmDai61RhNEJY7kgH9iw4qYJp6j8lDexpwVJ0@z \
    --to=tibequadorian@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).