Split Chrome and Chromium #23
Closed
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
added 2 commits
April 16, 2017 18:10
|
Can you please remove the following line in the .travis.yml and tray to build again:
|
Related to #22 Split Chrome and Chromium
|
Sadly, that didn't help. Now only Chromium is being recognized (as it should be), but still exiting with exit code |
|
Very strange. I will have a look at other repos which use chromium. Maybe I can find the issue. |
|
@4kochi I made a pullrequest on karma-runner/karma#2664 to print the stdout and stderr. You might find it useful. |
|
It turns out the flaky test failures are fixed by always running Chrome/Chromium in headless mode on Travis. I fixed it here: #27 |
|
Fixed by #27 |
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.
Related to #22
This was supposed to be easy, a simple split, however now travis says Chromium can't connect even though Chrome works fine with
CHROME_BIN=chromium-browser. Logs are hereI'd be happy to investigate further, but I simply cannot reproduce the issue on my machine. Even forced on a VM. Suggestions are welcome.