Smart-proxy rake test fails for me

Hi Folks,
I am attempting to run the smart-proxy tests and am getting some errors.
I suspect a mismatched gem somewhere. Could someone confirm that this
selection of gems is correct for running under ruby-2.0.0-p353?
Alternatively could I get a copy of this information from the Jenkins CI
environment?

pkelly@vihla676(theforeman-develop): bundle list
Gems included by the bundle:

  • addressable (2.3.8)
  • ast (2.2.0)
  • builder (3.2.2)
  • bundler (1.9.6)
  • ci_reporter (1.9.3)
  • coderay (1.1.1)
  • crack (0.4.3)
  • facter (2.4.6)
  • ffi (1.9.10)
  • gssapi (1.2.0)
  • hashdiff (0.3.0)
  • hiera (1.3.4)
  • json (1.8.3)
  • json_pure (1.8.3)
  • metaclass (0.0.4)
  • method_source (0.8.2)
  • mocha (0.13.3)
  • parser (2.3.1.2)
  • powerpack (0.1.1)
  • pry (0.10.3)
  • puppet (3.7.5)
  • rack (1.5.5)
  • rack-protection (1.5.3)
  • rack-test (0.6.3)
  • rainbow (2.1.0)
  • rake (10.4.2)
  • rake-compiler (0.9.9)
  • rdoc (4.2.0)
  • rkerberos (0.1.3)
  • rubocop (0.38.0)
  • rubocop-checkstyle_formatter (0.2.0)
  • ruby-augeas (0.5.0)
  • ruby-libvirt (0.6.0)
  • ruby-progressbar (1.8.1)
  • rubyipmi (0.10.0)
  • safe_yaml (1.0.4)
  • sinatra (1.4.7)
  • single_test (0.6.0)
  • slop (3.6.0)
  • smart_proxy (1.13.0.develop)
  • test-unit (2.0.0.0)
  • tilt (1.4.1)
  • unicode-display_width (1.0.5)
  • webmock (2.1.0)

Thanks In Advance ,
Paul

> Hi Folks,

Hi!

> I am attempting to run the smart-proxy tests and am getting some errors.
> I suspect a mismatched gem somewhere. Could someone confirm that this
> selection of gems is correct for running under ruby-2.0.0-p353?
> Alternatively could I get a copy of this information from the Jenkins CI
> environment?

You can see what gems are installed here:

http://ci.theforeman.org/job/test_proxy_develop_pr_core/804/puppet=4.3.0,ruby=2.0.0/consoleFull

Anyway, what errors are you seeing when you run tests? Have you tried
'bundle exec rake test' (that uses gems in the smart-proxy bundle)?

··· On 06/07, paul kelly wrote:


Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

http://ci.theforeman.org/job/test_proxy_develop/ is the test job, linked
from the README if you need it in future.

http://ci.theforeman.org/job/test_proxy_develop/puppet=3.8.0,ruby=2.0.0/lastSuccessfulBuild/console
is the last run for Ruby 2.0.0, scroll most of the way down past the RVM
setup to find the gem list.

··· On 07/06/16 14:11, paul kelly wrote: > Hi Folks, > I am attempting to run the smart-proxy tests and am getting some > errors. I suspect a mismatched gem somewhere. Could someone confirm that > this selection of gems is correct for running under ruby-2.0.0-p353? > Alternatively could I get a copy of this information from the Jenkins CI > environment?


Dominic Cleal
dominic@cleal.org

Nice!!

Thanks Daniel but everything is now working fine. You just have to use the
right gems. . . . .

··· On 7 June 2016 at 15:03, Daniel Lobato Garcia wrote:

On 06/07, paul kelly wrote:

Hi Folks,

Hi!

I am attempting to run the smart-proxy tests and am getting some
errors.
I suspect a mismatched gem somewhere. Could someone confirm that this
selection of gems is correct for running under ruby-2.0.0-p353?
Alternatively could I get a copy of this information from the Jenkins CI
environment?

You can see what gems are installed here:

http://ci.theforeman.org/job/test_proxy_develop_pr_core/804/puppet=4.3.0,ruby=2.0.0/consoleFull

Anyway, what errors are you seeing when you run tests? Have you tried
’bundle exec rake test’ (that uses gems in the smart-proxy bundle)?


Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.