Enable Chrome Canary tests on Travis

Enable Chrome Canary browser tests on Travis

I created a karma branch to test this on travis - see bottom of the log here:
https://travis-ci.org/dart-lang/dev_compiler/jobs/68106290

R=jmesserly@google.com

Committed: https://github.com/dart-lang/dev_compiler/commit/eb3ce0f239305bef7729b5e844e8a0c05a3058f0

[vsm, 2015-06-24 13:21:01]

vsm@google.com changed reviewers:
+ jmesserly@google.com

[Jennifer Messerly, 2015-06-24 15:44:23]

minor comments, but LGTM!

https://codereview.chromium.org/1205043002/diff/1/.travis.yml
File .travis.yml (right):

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode7
.travis.yml:7: - pub global activate dart_coveralls
we may want to move these into a script at some point?
seems alright now though, hard to complain about a 20 line file :)

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode16
.travis.yml:16: - npm install
I think this is normally the "install" step:
http://docs.travis-ci.com/user/customizing-the-build/#Customizing-the-Install...

not sure it matters, or what the difference is between before_install and
install.

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode19
.travis.yml:19: - ./node_modules/karma/bin/karma start --single-run
should this be part of presubmit?

https://codereview.chromium.org/1205043002/diff/1/karma.conf.js
File karma.conf.js (right):

https://codereview.chromium.org/1205043002/diff/1/karma.conf.js#newcode23
karma.conf.js:23: 'lib/runtime/dart_*.js',
could we just include everything under lib/runtime?
that way if we change our naming convention we won't need to edit this

[vsm, 2015-06-24 17:19:55]

https://codereview.chromium.org/1205043002/diff/1/.travis.yml
File .travis.yml (right):

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode7
.travis.yml:7: - pub global activate dart_coveralls
On 2015/06/24 15:44:22, John Messerly wrote:
> we may want to move these into a script at some point?
> seems alright now though, hard to complain about a 20 line file :)

This might be useful if we want to automatically get the latest canary rather
than rely on user installation (for our own local runs).  I'll leave it here for
now though.

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode16
.travis.yml:16: - npm install
On 2015/06/24 15:44:22, John Messerly wrote:
> I think this is normally the "install" step:
>
http://docs.travis-ci.com/user/customizing-the-build/#Customizing-the-Install...
> 
> not sure it matters, or what the difference is between before_install and
> install.

I tried to redo the steps to better match that (and tested on the karma branch).

https://codereview.chromium.org/1205043002/diff/1/.travis.yml#newcode19
.travis.yml:19: - ./node_modules/karma/bin/karma start --single-run
On 2015/06/24 15:44:22, John Messerly wrote:
> should this be part of presubmit?

I wanted to make you guys could run it first.  :-)

[vsm, 2015-06-24 17:21:03]

https://codereview.chromium.org/1205043002/diff/1/karma.conf.js
File karma.conf.js (right):

https://codereview.chromium.org/1205043002/diff/1/karma.conf.js#newcode23
karma.conf.js:23: 'lib/runtime/dart_*.js',
On 2015/06/24 15:44:22, John Messerly wrote:
> could we just include everything under lib/runtime?
> that way if we change our naming convention we won't need to edit this

Unfortunately, that pulls in the message widget file as well.  We could move
that to a different directory.  WDYT?

[vsm, 2015-06-24 17:21:19]

Committed patchset #2 (id:20001) manually as
eb3ce0f239305bef7729b5e844e8a0c05a3058f0 (presubmit successful).