From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/elasticsearch-transport/
Date: Sun, 27 May 2018 07:19:53 +0000 (UTC) [thread overview]
Message-ID: <1527405588.a6c617409db4a63aac10cd67fb386b0e5c935c8a.graaff@gentoo> (raw)
commit: a6c617409db4a63aac10cd67fb386b0e5c935c8a
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun May 27 07:19:27 2018 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun May 27 07:19:48 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a6c61740
dev-ruby/elasticsearch-transport: run unit tests
Package-Manager: Portage-2.3.36, Repoman-2.3.9
.../elasticsearch-transport-5.0.5.ebuild | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/dev-ruby/elasticsearch-transport/elasticsearch-transport-5.0.5.ebuild b/dev-ruby/elasticsearch-transport/elasticsearch-transport-5.0.5.ebuild
index b3c5e1ac179..e27df7cddeb 100644
--- a/dev-ruby/elasticsearch-transport/elasticsearch-transport-5.0.5.ebuild
+++ b/dev-ruby/elasticsearch-transport/elasticsearch-transport-5.0.5.ebuild
@@ -5,7 +5,9 @@ EAPI=6
USE_RUBY="ruby23 ruby24"
RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
-RUBY_FAKEGEM_TASK_DOC=doc
+RUBY_FAKEGEM_RECIPE_DOC=rdoc
+
+RUBY_FAKEGEM_TASK_TEST="NOTURN=true test"
inherit ruby-fakegem
@@ -30,13 +32,11 @@ ruby_add_bdepend "
dev-ruby/mocha:1.0
dev-ruby/pry
dev-ruby/shoulda-context
+ dev-ruby/curb
+ dev-ruby/patron
)
"
-# Tests need additional modules (at least 'turn') packaged. Then someone
-# should look into running them and so on.
-RESTRICT="test"
-
RUBY_S=${MY_P}/${PN}
all_ruby_prepare() {
@@ -47,4 +47,8 @@ all_ruby_prepare() {
sed -e '/bundler/d' \
-e '/require.*cane/,/end/d' \
-i Rakefile || die
+
+ # Tweak test setup to only run unit tests since we don't have a live cluster
+ sed -i -e "s/RUBY_VERSION > '1.9'/false/" \
+ -e '/module Elasticsearch/,$ s:^:#:' test/test_helper.rb || die
}
next reply other threads:[~2018-05-27 7:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 7:19 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-06 14:06 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/elasticsearch-transport/ Hans de Graaff
2024-11-15 10:32 Hans de Graaff
2024-06-09 9:20 Hans de Graaff
2024-05-25 9:17 Hans de Graaff
2024-05-25 9:17 Hans de Graaff
2024-02-18 6:59 Hans de Graaff
2023-12-17 9:36 Hans de Graaff
2023-09-29 6:14 Hans de Graaff
2023-09-06 5:34 Hans de Graaff
2023-07-18 5:50 Hans de Graaff
2023-07-08 6:04 Hans de Graaff
2023-04-01 8:26 Hans de Graaff
2023-04-01 8:26 Hans de Graaff
2022-05-08 7:28 Hans de Graaff
2021-07-27 6:30 Hans de Graaff
2021-07-23 11:58 Hans de Graaff
2021-07-23 11:58 Hans de Graaff
2021-07-12 13:26 Hans de Graaff
2020-05-24 4:14 Hans de Graaff
2020-05-23 18:49 Hans de Graaff
2020-05-23 18:49 Hans de Graaff
2020-05-02 5:18 Hans de Graaff
2020-01-31 8:46 Hans de Graaff
2019-11-16 9:36 Hans de Graaff
2019-06-30 7:23 Hans de Graaff
2019-06-08 8:00 Michał Górny
2019-05-25 6:22 Hans de Graaff
2019-05-09 5:54 Hans de Graaff
2019-05-04 6:50 Hans de Graaff
2019-04-15 15:31 Hans de Graaff
2019-04-11 18:29 Hans de Graaff
2018-08-01 6:07 Hans de Graaff
2018-05-27 6:42 Hans de Graaff
2017-10-14 16:19 Michał Górny
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=1527405588.a6c617409db4a63aac10cd67fb386b0e5c935c8a.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