public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Louis Sautier" <sbraz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/colorama/
Date: Wed, 22 Aug 2018 15:12:50 +0000 (UTC)	[thread overview]
Message-ID: <1534950751.870b8bb277eb7d876ff8d5482a0b1454fa6b3784.sbraz@gentoo> (raw)

commit:     870b8bb277eb7d876ff8d5482a0b1454fa6b3784
Author:     Louis Sautier <sbraz <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 22 09:05:51 2018 +0000
Commit:     Louis Sautier <sbraz <AT> gentoo <DOT> org>
CommitDate: Wed Aug 22 15:12:31 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=870b8bb2

dev-python/colorama: run tests with 'script' to make stdout a TTY

Package-Manager: Portage-2.3.48, Repoman-2.3.10

 dev-python/colorama/colorama-0.3.9-r1.ebuild | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/dev-python/colorama/colorama-0.3.9-r1.ebuild b/dev-python/colorama/colorama-0.3.9-r1.ebuild
index 05ea77f60e5..31476d291ca 100644
--- a/dev-python/colorama/colorama-0.3.9-r1.ebuild
+++ b/dev-python/colorama/colorama-0.3.9-r1.ebuild
@@ -36,9 +36,8 @@ python_install_all() {
 }
 
 python_test() {
-	# Skip two tests which seem to fail when stdout isn't a TTY
+	# Some tests require stdout to be a TTY
 	# https://github.com/tartley/colorama/issues/169
-	pytest -vv -k "not (testInitDoesntWrapOnEmulatedWindows \
-		or testInitDoesntWrapOnNonWindows)" \
+	script -eqc "pytest -vv -s" /dev/null \
 		|| die "tests failed with ${EPYTHON}"
 }


             reply	other threads:[~2018-08-22 15:12 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 15:12 Louis Sautier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-25  2:26 [gentoo-commits] repo/gentoo:master commit in: dev-python/colorama/ Sam James
2023-05-29 12:26 Michał Górny
2022-11-25 13:58 Michał Górny
2022-11-25 13:53 Arthur Zamarin
2022-10-25  8:28 Michał Górny
2022-07-24 20:29 Michał Górny
2022-07-24 19:13 Sam James
2022-06-17  6:02 Michał Górny
2022-06-12 14:25 Michał Górny
2022-06-12 11:53 Sam James
2022-05-11 17:54 Michał Górny
2022-05-11 17:54 Michał Górny
2021-10-17  7:41 Michał Górny
2021-05-06 18:45 Michał Górny
2020-11-14 22:50 Sam James
2020-10-15 11:00 Michał Górny
2020-09-20  8:35 Michał Górny
2020-05-31 15:42 Michał Górny
2020-05-04 10:29 Michał Górny
2020-04-26 20:40 Michał Górny
2020-04-26 20:40 Michał Górny
2020-03-26 14:51 Michał Górny
2020-03-26 14:51 Michał Górny
2020-03-26 14:51 Michał Górny
2020-01-27 11:50 Mikle Kolyada
2020-01-13 18:34 Sebastian Pipping
2020-01-13  8:50 Agostino Sarubbo
2020-01-13  8:25 Sergei Trofimovich
2020-01-12 23:22 Sergei Trofimovich
2020-01-12 22:53 Sergei Trofimovich
2020-01-12 22:42 Sergei Trofimovich
2020-01-10 22:30 Sergei Trofimovich
2019-12-03  3:02 Aaron Bauman
2019-12-03  2:19 Patrick McLean
2018-12-27  8:27 Tim Harder
2018-10-31 17:58 Sebastian Pipping
2018-08-21 23:09 Louis Sautier
2017-05-21 22:15 Patrice Clement
2017-04-26  8:20 Tim Harder
2017-02-10 19:53 Zac Medico
2016-03-19 14:19 Manuel Rüger
2016-03-02  7:37 Andrey Grozin
2016-02-24  8:37 Justin Lecher
2016-02-23 12:08 Justin Lecher
2016-01-10  8:23 Justin Lecher
2015-12-13 14:05 Justin Lecher
2015-11-23 10:05 Justin Lecher
2015-11-23 10:05 Justin Lecher
2015-11-23  6:44 Jeroen Roovers
2015-11-22  8:20 Markus Meier
2015-10-10 18:49 Mikle Kolyada
2015-09-29 20:49 Markus Meier
2015-09-22 17:36 Tobias Klausmann
2015-09-08  8:16 Joshua Kinard
2015-09-06  5:20 Jeroen Roovers
2015-08-25 23:23 Mike Gilbert

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=1534950751.870b8bb277eb7d876ff8d5482a0b1454fa6b3784.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