public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/pytest-randomly/
Date: Tue, 19 May 2020 11:13:23 +0000 (UTC)	[thread overview]
Message-ID: <1589886793.238d11bdd648daa411015f6e07b1052bdaa0aaad.andrewammerlaan@gentoo> (raw)
Message-ID: <20200519111323.2wl_5Ao8uAbylKqGpPPDtzF-JPewJfnxtz9y_bJgstw@z> (raw)

commit:     238d11bdd648daa411015f6e07b1052bdaa0aaad
Author:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Tue May 19 11:13:13 2020 +0000
Commit:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Tue May 19 11:13:13 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=238d11bd

dev-python/pytest-randomly: make repoman happy

repoman was complaing about the lines starting with spaces

also, tests don't seem to be working

Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>

 dev-python/pytest-randomly/pytest-randomly-3.3.1-r1.ebuild | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/dev-python/pytest-randomly/pytest-randomly-3.3.1-r1.ebuild b/dev-python/pytest-randomly/pytest-randomly-3.3.1-r1.ebuild
index 7aa75e0..89096d8 100644
--- a/dev-python/pytest-randomly/pytest-randomly-3.3.1-r1.ebuild
+++ b/dev-python/pytest-randomly/pytest-randomly-3.3.1-r1.ebuild
@@ -18,14 +18,17 @@ SRC_URI="https://github.com/pytest-dev/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz
 LICENSE="BSD"
 SLOT="0"
 KEYWORDS="~amd64 ~x86"
-IUSE="test"
-RESTRICT="!test? ( test )"
+
+# many failures, both with pytest-5 and 4
+RESTRICT="test"
+
 RDEPEND="
 	dev-python/docutils[${PYTHON_USEDEP}]
 	dev-python/factory_boy[${PYTHON_USEDEP}]
 	dev-python/faker[${PYTHON_USEDEP}]
 	dev-python/numpy[${PYTHON_USEDEP}]
 	dev-python/pygments[${PYTHON_USEDEP}]
+	dev-python/pytest[${PYTHON_USEDEP}]
 
 	$(python_gen_cond_dep 'dev-python/importlib_metadata[${PYTHON_USEDEP}]' python3_6 python3_7)
 "
@@ -44,7 +47,9 @@ DEPEND="
 #		$(python_gen_cond_dep 'dev-python/check-manifest[${PYTHON_USEDEP}]' python3_8)
 #		dev-python/multilint[${PYTHON_USEDEP}]
 
+distutils_enable_tests pytest
+
 python_test() {
-    distutils_install_for_testing
-    pytest -vv || die "Testsuite failed under ${EPYTHON}"
+	distutils_install_for_testing
+	pytest -vv || die "Testsuite failed under ${EPYTHON}"
 }


             reply	other threads:[~2020-05-19 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 11:24 Andrew Ammerlaan [this message]
2020-05-19 11:13 ` [gentoo-commits] repo/proj/guru:dev commit in: dev-python/pytest-randomly/ Andrew Ammerlaan
  -- strict thread matches above, loose matches on Subject: below --
2023-03-16 13:59 [gentoo-commits] repo/proj/guru:master " Florian Schmaus
2022-06-01 11:17 Andrew Ammerlaan
2021-11-03 11:12 Andrew Ammerlaan
2021-06-15  7:11 Andrew Ammerlaan
2021-04-14  9:08 Andrew Ammerlaan
2020-12-18 19:05 Andrew Ammerlaan
2020-12-10  8:46 Andrew Ammerlaan
2020-08-28 15:26 Andrew Ammerlaan
2020-05-21 11:24 Andrew Ammerlaan
2020-05-19 11:24 Andrew Ammerlaan
2020-04-28  7:44 Andrew Ammerlaan

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=1589886793.238d11bdd648daa411015f6e07b1052bdaa0aaad.andrewammerlaan@gentoo \
    --to=andrewammerlaan@riseup.net \
    --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