Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support google-chrome-stable, chromium-browser, and chromium #41

Merged
merged 1 commit into from
Apr 16, 2015

Conversation

Krinkle
Copy link
Contributor

@Krinkle Krinkle commented Mar 20, 2015

See issue #17.

zzo added a commit that referenced this pull request Apr 16, 2015
Support google-chrome-stable, chromium-browser, and chromium
@zzo zzo merged commit 719533d into karma-runner:master Apr 16, 2015
@Krinkle Krinkle deleted the chromium branch April 16, 2015 04:00
Krinkle added a commit to wikimedia/unicodejs that referenced this pull request Apr 29, 2015
* Add grunt-cli so that users don't need grunt-cli pre-installed globally.

* karma-coverage@0.3.0
  Fixes karma-runner/karma-coverage#24

* karma-chrome-launcher@0.1.8
  Fixes karma-runner/karma-chrome-launcher#41.
  This will allow our Jenkins setup to rid the CHROME_BIN hack, after all
  projects have updated.

* grunt-jscs@1.8.0: Addresses T90816.

Change-Id: I49eb93e590e475536bbaaa30b83ea888390190d2
wmfgerrit pushed a commit to wikimedia/integration-zuul-config that referenced this pull request Mar 8, 2016
CHROME_BIN is no more needed since karma-chrome-launcher v0.1.8 and Timo
patch:
karma-runner/karma-chrome-launcher#41

By setting DISPLAY directly from Zuul, we remove some logic from the
slave-scripts. A baby step toward phasing them out.

Bug: T128090
Signed-off-by: Antoine Musso <hashar@free.fr>
Change-Id: If026b795d66c3d3c0f3d35b74bfe54d49dd93e69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants