From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/rbtools/
Date: Sun, 29 Aug 2021 07:55:22 +0000 (UTC) [thread overview]
Message-ID: <1630223717.719794bb060cd1d3faa52c3eea2e03207e247cc7.graaff@gentoo> (raw)
commit: 719794bb060cd1d3faa52c3eea2e03207e247cc7
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 29 07:41:39 2021 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Aug 29 07:55:17 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=719794bb
dev-util/rbtools: fix tests
Run tests against an installed version to ensure the CLI tests work as
expected.
Closes: https://bugs.gentoo.org/809476
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-util/rbtools/rbtools-2.0.1.ebuild | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dev-util/rbtools/rbtools-2.0.1.ebuild b/dev-util/rbtools/rbtools-2.0.1.ebuild
index 4a077b612df..7baa5961051 100644
--- a/dev-util/rbtools/rbtools-2.0.1.ebuild
+++ b/dev-util/rbtools/rbtools-2.0.1.ebuild
@@ -45,3 +45,8 @@ src_prepare() {
# Avoid tests requiring unpackaged test data
rm -f rbtools/clients/tests/test_scanning.py || die
}
+
+python_test() {
+ distutils_install_for_testing
+ distutils-r1_python_test
+}
next reply other threads:[~2021-08-29 7:55 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 7:55 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-08 10:27 [gentoo-commits] repo/gentoo:master commit in: dev-util/rbtools/ Hans de Graaff
2024-12-08 10:27 Hans de Graaff
2024-12-04 11:25 Hans de Graaff
2024-12-01 11:38 Hans de Graaff
2024-03-08 11:35 Hans de Graaff
2023-07-19 10:14 Jakov Smolić
2023-07-19 10:14 Jakov Smolić
2023-06-11 11:50 Hans de Graaff
2023-06-11 11:50 Hans de Graaff
2023-06-06 17:52 Arthur Zamarin
2023-02-14 6:56 Hans de Graaff
2023-01-14 11:47 Sam James
2023-01-14 11:47 Sam James
2022-12-19 6:51 Hans de Graaff
2022-12-05 18:24 Hans de Graaff
2022-12-05 18:24 Hans de Graaff
2022-11-12 13:52 Hans de Graaff
2022-10-30 6:48 Hans de Graaff
2022-10-25 12:50 Sam James
2022-10-25 9:08 Sam James
2022-10-25 6:02 Hans de Graaff
2022-10-05 5:33 Hans de Graaff
2022-09-01 0:36 Sam James
2022-06-24 20:59 Jakov Smolić
2022-06-17 4:52 Hans de Graaff
2022-05-22 5:29 Hans de Graaff
2022-05-21 9:47 Hans de Graaff
2022-03-24 6:09 Hans de Graaff
2022-01-22 9:48 Agostino Sarubbo
2022-01-21 23:20 Sam James
2022-01-08 11:47 Hans de Graaff
2021-07-29 4:41 Hans de Graaff
2021-07-29 4:41 Hans de Graaff
2021-06-01 6:59 Agostino Sarubbo
2021-06-01 6:32 Agostino Sarubbo
2021-01-17 9:47 Hans de Graaff
2020-11-30 6:18 Hans de Graaff
2020-11-30 6:18 Hans de Graaff
2020-10-13 10:01 Agostino Sarubbo
2020-09-02 5:20 Hans de Graaff
2020-04-15 4:16 Hans de Graaff
2020-02-09 7:21 Hans de Graaff
2020-02-07 12:12 Agostino Sarubbo
2020-02-06 8:21 Agostino Sarubbo
2020-02-04 17:04 Hans de Graaff
2020-02-04 15:40 Michał Górny
2019-10-02 19:08 Agostino Sarubbo
2019-10-02 18:53 Agostino Sarubbo
2019-09-28 6:03 Hans de Graaff
2019-09-28 6:03 Hans de Graaff
2019-09-06 19:11 Andreas Sturmlechner
2018-01-25 11:51 Michael Palimaka
2017-10-12 12:15 Michael Palimaka
2017-10-12 12:15 Michael Palimaka
2017-06-03 16:17 Michael Palimaka
2017-04-27 12:17 Michael Palimaka
2017-04-23 10:27 Agostino Sarubbo
2017-01-19 17:14 Johannes Huber
2017-01-19 17:14 Johannes Huber
2017-01-12 18:35 Michael Palimaka
2016-11-24 12:37 Michael Palimaka
2016-06-23 19:57 Michael Palimaka
2016-06-23 19:57 Michael Palimaka
2016-04-27 11:49 Michael Palimaka
2016-02-14 14:12 Michael Palimaka
2016-01-27 9:22 Agostino Sarubbo
2015-10-27 17:11 Michael Palimaka
2015-09-20 15:18 Michael Palimaka
2015-09-19 13:30 Agostino Sarubbo
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=1630223717.719794bb060cd1d3faa52c3eea2e03207e247cc7.graaff@gentoo \
--to=graaff@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