Test to fix issue #892 with chrome version change from stable to beta #894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In order to try help diagnosis, I just asked travis to re-run previously passing build 1417.4 https://travis-ci.org/reactjs/react-rails/builds/338407498 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Trying to determine what causes 3 of 21 builds to fail, per Issue #892. I already compared the previous working build's gem versions to the broken build and did not find any differences.
The new version of Chrome (from version 64.0.3282.167-1 to 66.0.3359.139-1) might have affected the build, so I want to try to change the Chrome version. It's installed in the travis.yml file, but you're only allowed to specify stable or beta as the version, not a number version of chrome.
I'm creating this pull request because I want to test this change within a Travis build.