Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Avoid Ruby warning by removing an "interesting" whitespace #36

Merged
merged 13 commits into from Nov 18, 2017

Conversation

olleolleolle
Copy link
Contributor

@olleolleolle olleolleolle commented Aug 28, 2017

This PR wants to fix a Ruby warning emitted:

parentheses after method name is interpreted as an argument list, not a decomposed argument

This appears when running Sinatra's test suite.

https://api.travis-ci.org/jobs/268657054/log.txt?deansi=true


In order to get a green build for this, I went down the rabbit hole and tried to make it green.

  - warning emitted: parentheses after method name is interpreted as an argument list, not a decomposed argument
@olleolleolle olleolleolle changed the title Avoid warning by removing whitespace Avoid Ruby warning by removing an "interesting" whitespace Aug 28, 2017
@jdantonio
Copy link
Member

I have no idea why such an innocuous change broke the build. Rebuilding...

@olleolleolle
Copy link
Contributor Author

Thank you for responding so quickly!

@olleolleolle
Copy link
Contributor Author

olleolleolle commented Aug 29, 2017

@jdantonio rbx-2 no longer exists as a target to build to. it's called something else. Perhaps rbx-3?

Perhaps - rbx-3.69?


I can see the CI matrix is a little outdated. There are a few newer versions out.

@olleolleolle
Copy link
Contributor Author

olleolleolle commented Aug 29, 2017

@jdantonio So, I have now reinstated rbx as a build target, to find that it can now fail at running RSpec built-in matchers.

Am I allowed to move rbx to allowed_failures until somebody can fix that build?

Example failing build of rbx-3.84: https://travis-ci.org/ruby-concurrency/ref/jobs/269596964

@jdantonio
Copy link
Member

@olleolleolle Absolutely! The rbx community has gotten upset with me in the past for putting it in allowed failures, but there are pragmatic realities we need to consider. Please move it. And thank you very much for all your hard work!

Would you like commit rights to this repo? I'm not heavily involved in this project any more (sadly, I am not working with Ruby in my current job 😞) so I'd love any assistance you are interested in giving.

@olleolleolle
Copy link
Contributor Author

@jdantonio For this project, I'm more of an arm-chair patcher than an on-the-frontline maintainer.

I'm comfortable with a slower rate of merges than "me pushing a big green button with no one knowing".

@olleolleolle
Copy link
Contributor Author

@jdantonio I'm right now adding an RSpec 3.6 update to the Gemfile, to see if that can placate rbx, just one more go at the till before it's finally put in allowed_failures.

@olleolleolle
Copy link
Contributor Author

olleolleolle commented Aug 29, 2017

@jdantonio (About rbx) That made the test suite pass! It didn't, however, make the job end, which will make it time out, I believe.

@olleolleolle
Copy link
Contributor Author

@jdantonio I will now update coveralls to latest release, as well. Docs on Coveralls

@olleolleolle
Copy link
Contributor Author

@jdantonio There! A green build!

.travis.yml Outdated
before_install:
- gem update --system
- gem install bundler
after_success:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a feeling this is not needed!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sent a commit to skip that step.

@olleolleolle
Copy link
Contributor Author

@jdantonio How do you like it, now?

@pitr-ch
Copy link
Member

pitr-ch commented Nov 18, 2017

@olleolleolle Thanks!

@pitr-ch
Copy link
Member

pitr-ch commented Nov 18, 2017

I appreciate your help.

@pitr-ch pitr-ch merged commit 7a3991f into ruby-concurrency:master Nov 18, 2017
@olleolleolle olleolleolle deleted the fix/avoid-a-ruby-warning branch November 18, 2017 11:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants