opened
dwradcliffe
username_0
Let's speed up and simplify tests by skipping ruby-head. It hasn't worked for a very long time and doesn't seem to be related to any of our code.

@username_4 @username_1
stop testing ruby-head since it never works
issue
created
qrush
username_1
:gun:
comment
created
sferik
username_2
:confused: I don’t think this is the right decision.

This element in the build matrix was set to `allow_failures` and `fast_finish`, so the overall build status was not affected or blocked by it.

The fact that `ruby-head` is failing now is not a problem, but as we get closer to the next Ruby release, this information will be more relevant, both to us and the Ruby core team.

If the decision stands to remove this, the entire `matrix` section of `.travis.yml` should also be removed, since it is only relevant to this build.
comment
created
qrush
username_1
I wasn't aware it was being used to inform ruby-core of things. Has it been used before for any decision making re: releases?
comment
created
indirect
username_3
As long as `allow_failure` and `fast_finish` are both turned on, isn't this useful data to have? It doesn't cost us anything, and it seems good to know. (We do this on the Bundler travis build as well).
comment
created
arthurnn
username_4
yeah, i think i will revert this.
comment
created
dwradcliffe
username_0
Sounds good. I don't think this really will help us upgrade sooner, since ruby-head is probably always ahead of any release we might use. But I'm ok testing if we can help ruby-core. :+1:
comment
created
sferik
username_2
I’m happy to work on a team that can merge fast but then reconsider. :smile:
comment