Spec: Events.registry exercised

[olleolleolle]

This PR adds a unit test which calls the method Events.registry, in order to exercise the code. See #1124

---

Eh, also: work to get rid of all the Ruby warnings, to prepare to enable --warnings in .rspec.

[brasmusson]

The warning fixes should be split out to a separate PR, especially since the choice of not to use parenthesis is very deliberate.

[olleolleolle]

@brasmussen Thanks for the feedback! I agree that splitting this makes sense, and I'll get to it in a few days.

Thanks also for linking to discussions. It makes it possible to learn the why of things.

[olleolleolle]

The JRuby test fails on both 9.1.10.0 and on 9.1.12.0 on this feature:

(::) failed steps (::)
process still alive after 60 seconds (ChildProcess::TimeoutError)
features/docs/raketask.feature:38:in `When I run `bundle exec rake pass`'

process still alive after 60 seconds (ChildProcess::TimeoutError)
features/docs/raketask.feature:42:in `When I run `bundle exec rake fail`'

Failing Scenarios:
  cucumber -p ruby features/docs/raketask.feature:37 # Scenario: Passing feature
  cucumber -p ruby features/docs/raketask.feature:41 # Scenario: Failing feature

208 scenarios (2 failed, 206 passed)

master is building the other code.

[mattwynne]

@olleolleolle that could just be a flicker. The JRuby tests can be really slow. Can you try triggering a rebuild?

[olleolleolle]

I can do that, again.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.