"warning: couldn't activate the test plugin, skipping"

[Mike Dalessio]

Hi, using Hoe 3.17.10 I'm able to run rake test just fine in Nokogiri.

Once I update to Hoe 3.18.0, though, it breaks and I only see the warning output: warning: couldn't activate the test plugin, skipping.

See #95 for reasons why I'm unable to easily narrow this problem down to a specific commit.

[Ryan Davis]

Seems to work fine for me?

% git diff
diff --git a/Gemfile b/Gemfile
index e85d4073..b32e0abe 100644
--- a/Gemfile
+++ b/Gemfile
@@ -7,7 +7,7 @@ source "https://rubygems.org/"
 gem "mini_portile2", "~>2.4.0"
 
 gem "concourse", "~>0.24", :group => [:development, :test]
-gem "hoe", "=3.17", :group => [:development, :test]
+gem "hoe", "~>3.18", :group => [:development, :test]
 gem "hoe-bundler", "~>1.2", :group => [:development, :test]
 gem "hoe-debugging", "~>2.0", :group => [:development, :test]
 gem "hoe-gemspec", "~>1.0", :group => [:development, :test]

% rake test
/Users/ryan/Work/git/sparklemotion/nokogiri/test/helper.rb:29: version info: {"warnings"=>[], "nokogiri"=>"1.10.4", "ruby"=>{"version"=>"2.5.5", "platform"=>"x86_64-darwin18", "description"=>"ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-darwin18]", "engine"=>"ruby"}, "libxml"=>{"binding"=>"extension", "source"=>"packaged", "libxml2_path"=>"/Users/ryan/Work/git/sparklemotion/nokogiri/ports/x86_64-apple-darwin18.6.0/libxml2/2.9.9", "libxslt_path"=>"/Users/ryan/Work/git/sparklemotion/nokogiri/ports/x86_64-apple-darwin18.6.0/libxslt/1.1.33", "libxml2_patches"=>["0001-Revert-Do-not-URI-escape-in-server-side-includes.patch", "0002-Remove-script-macro-support.patch", "0003-Update-entities-to-remove-handling-of-ssi.patch"], "libxslt_patches"=>["0001-Fix-security-framework-bypass.patch"], "compiled"=>"2.9.9", "loaded"=>"2.9.9"}}
Coverage report generated for MiniTest to /Users/ryan/Work/git/sparklemotion/nokogiri/coverage. 1099 / 2369 LOC (46.39%) covered.
Run options: --seed 61688

# Running:

...........................................................................................S......................................................................................................................................................................................................................................................................S...................................................................................................................................................................................................................................................................................................................................................................................S.........................................................................................................................SS..........................................................................................S.S........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................S......................................S.......S..............

Fabulous run in 5.984416s, 249.4813 runs/s, 701.9900 assertions/s.

1493 runs, 4201 assertions, 0 failures, 0 errors, 10 skips

You have skipped tests. Run with --verbose for details.

As far as debugging why, I usually use ruby -dS rake faketask and look for the exceptions raised before any messages about the plugin in question.

[Mike Dalessio]

I can't reproduce it now. Closing.

[Ryan Davis]

I wonder why... I certainly had a period where that shit was unstable, but that was unreleased. You're never going against my git repo, right?

[Mike Dalessio]

Ummm ... it's remotely possible that I was doing something like gem 'hoe', :path => "../hoe", though I'm almost positive I tried with the official release before filing this.