From: "Louis Sautier" <sbraz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/blessed/
Date: Mon, 27 Apr 2020 19:11:22 +0000 (UTC) [thread overview]
Message-ID: <1588013645.4462a5eb4a5c8f020ab5d8cc3dd7ed61bc8c363a.sbraz@gentoo> (raw)
commit: 4462a5eb4a5c8f020ab5d8cc3dd7ed61bc8c363a
Author: Louis Sautier <sbraz <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 27 18:54:05 2020 +0000
Commit: Louis Sautier <sbraz <AT> gentoo <DOT> org>
CommitDate: Mon Apr 27 18:54:05 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4462a5eb
dev-python/blessed: enable all tests
This should have been done in the initial commit, I forgot to change the
test function.
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Louis Sautier <sbraz <AT> gentoo.org>
dev-python/blessed/blessed-1.17.5.ebuild | 3 ---
1 file changed, 3 deletions(-)
diff --git a/dev-python/blessed/blessed-1.17.5.ebuild b/dev-python/blessed/blessed-1.17.5.ebuild
index 907f9aebfe7..18fe22388d9 100644
--- a/dev-python/blessed/blessed-1.17.5.ebuild
+++ b/dev-python/blessed/blessed-1.17.5.ebuild
@@ -45,9 +45,6 @@ python_test() {
# COLORTERM must not be truecolor
# See https://github.com/jquast/blessed/issues/162
# Ignore coverage options
- # Skip two failing tests
COLORTERM= pytest -vv --override-ini="addopts=" \
- --deselect tests/test_core.py::test_number_of_colors_without_tty \
- --deselect tests/test_core.py::test_number_of_colors_with_tty \
|| die "tests failed with ${EPYTHON}"
}
next reply other threads:[~2020-04-27 19:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 19:11 Louis Sautier [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-24 14:28 [gentoo-commits] repo/gentoo:master commit in: dev-python/blessed/ Michał Górny
2023-07-28 15:11 Michał Górny
2023-03-11 16:17 Michał Górny
2023-03-11 12:30 Arthur Zamarin
2023-02-26 20:22 Louis Sautier
2023-02-04 4:48 Michał Górny
2022-10-03 8:24 Agostino Sarubbo
2022-10-03 0:44 Sam James
2022-08-30 3:36 Yixun Lan
2022-06-17 8:10 Arthur Zamarin
2022-06-04 17:48 Michał Górny
2022-05-16 13:03 Michał Górny
2022-01-21 8:54 Arthur Zamarin
2022-01-20 23:26 Michał Górny
2021-10-17 7:33 Michał Górny
2021-09-21 7:54 Michał Górny
2021-06-14 21:44 Louis Sautier
2021-06-14 21:44 Louis Sautier
2021-05-09 19:59 Louis Sautier
2021-02-25 7:40 Michał Górny
2020-11-28 12:27 Louis Sautier
2020-10-15 7:19 Louis Sautier
2020-10-14 22:41 Louis Sautier
2020-09-18 14:28 Michał Górny
2020-08-24 12:58 Louis Sautier
2020-07-31 13:15 Louis Sautier
2020-06-08 10:22 Louis Sautier
2020-04-27 18:35 Louis Sautier
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=1588013645.4462a5eb4a5c8f020ab5d8cc3dd7ed61bc8c363a.sbraz@gentoo \
--to=sbraz@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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