Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cloud9 vm install generates many gem warnings on rake test #440

Closed
jywarren opened this issue Mar 23, 2016 · 4 comments
Closed

cloud9 vm install generates many gem warnings on rake test #440

jywarren opened this issue Mar 23, 2016 · 4 comments
Labels
testing issues are usually for adding unit tests, integration tests or any other tests for a feature

Comments

@jywarren
Copy link
Member

Running rake test on this in cloud9 passes, but there are lots of unrelated external warnings from the gems; these warnings are not shown when running this locally. Running: rake test > test.log can be used to view just the test results in a file.

Asked for how to suppress these warnings here: http://stackoverflow.com/questions/36185485/exclude-external-gem-warnings-when-running-rake-test-in-rails

I was running it based on the README.md's cloud9 install process, and while tests did all pass, you can't see them easily due to the warnings.

My test machine is here: https://c9.io/jywarren/plots2-sqlite/

Excerpted from SO here:

I'm trying to set up a cloud9 (https://c9.io) test install of my Rails 3.2 app, so that new developers can quickly get it up and running for submitting changes and running tests. All my tests pass, but they're mixed in with many many warnings related to different gems:

Loaded suite /usr/local/rvm/gems/ruby-2.1.2/gems/rake-11.1.1/lib/rake/rake_test_loader
Started
......

Finished in 0.22973343 seconds.
------
6 tests, 10 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
0% passed
------
26.12 tests/s, 43.53 assertions/s
Loaded suite /usr/local/rvm/gems/ruby-2.1.2/gems/rake-11.1.1/lib/rake/rake_test_loader
Started
............................................

Finished in 4.18306875 seconds.
------
44 tests, 77 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
/usr/local/rvm/gems/ruby-2.1.2/gems/composite_primary_keys-5.0.14/lib/composite_primary_keys/relation.rb:26: warning: previous definition of destroy was here
/usr/local/rvm/gems/ruby-2.1.2/gems/composite_primary_keys-5.0.14/lib/composite_primary_keys/relation.rb:10: warning: method redefined; discarding old delete
/usr/local/rvm/gems/ruby-2.1.2/gems/composite_primary_keys-5.0.14/lib/composite_primary_keys/relation.rb:10: warning: previous definition of delete was here
/usr/local/rvm/gems/ruby-2.1.2/gems/composite_primary_keys-5.0.14/lib/composite_primary_keys/relation.rb:26: warning: method redefined; discarding old destroy

... it continues and generates warnings for lots of other gems.

On my own Ubuntu/Debian machines, I don't see these warnings, and they make it hard to see the test results that are now interspersed among dozens of other lines of warnings.

Is there a way to suppress the warnings or configure my tests so that they don't trigger this level of verbosity?

@jywarren jywarren added the testing issues are usually for adding unit tests, integration tests or any other tests for a feature label Mar 23, 2016
@jywarren jywarren mentioned this issue Mar 23, 2016
4 tasks
@jywarren
Copy link
Member Author

There is -- RUBYOPT=W0 rake test:units -- but we should perhaps reduce the warnings, too?

@jywarren
Copy link
Member Author

@ananyo2012
Copy link
Member

@jywarren Is this problem still happening? I don't see these warnings in my cloud9 machine.

@jywarren
Copy link
Member Author

If not then let's close this; the Jun 24th link is helpful if it recurs. Thanks!

jywarren pushed a commit that referenced this issue May 29, 2018
Issue #440 has been resolved, so this line can be removed?
SrinandanPai pushed a commit to SrinandanPai/plots2 that referenced this issue May 5, 2019
Issue publiclab#440 has been resolved, so this line can be removed?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing issues are usually for adding unit tests, integration tests or any other tests for a feature
Projects
None yet
Development

No branches or pull requests

2 participants