Test packages with ddc on travis

Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode per commit on travis.

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something like this.

See try-run here:

https://travis-ci.org/dart-lang/sdk/builds/172066040

R=jmesserly@google.com

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

[vsm, 2016-10-31 18:24:39]

Description was changed from

==========
Test packages with ddc on travis
==========

to

==========
Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode
per commit on travis.  

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something
like this.
==========

[vsm, 2016-10-31 18:24:39]

vsm@google.com changed reviewers:
+ jmesserly@google.com, kevmoo@google.com, srawlins@google.com

[vsm, 2016-10-31 18:25:23]

Description was changed from

==========
Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode
per commit on travis.  

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something
like this.
==========

to

==========
Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode
per commit on travis.  

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something
like this.

See try-run here:

https://travis-ci.org/dart-lang/sdk/builds/172066040
==========

[Jennifer Messerly, 2016-10-31 23:35:51]

https://codereview.chromium.org/2465923003/diff/1/pkg/dev_compiler/tool/build...
File pkg/dev_compiler/tool/build_pkgs.sh (right):

https://codereview.chromium.org/2465923003/diff/1/pkg/dev_compiler/tool/build...
pkg/dev_compiler/tool/build_pkgs.sh:12: # Under pkg
should we just enumerate the directory? instead of hard coding

[Jennifer Messerly, 2016-10-31 23:38:38]

but lgtm for starters :)

[vsm, 2016-11-01 13:01:50]

Description was changed from

==========
Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode
per commit on travis.  

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something
like this.

See try-run here:

https://travis-ci.org/dart-lang/sdk/builds/172066040
==========

to

==========
Test packages with ddc on travis

Here's a setup to test build of various SDK packages with DDC and strong mode
per commit on travis.

It's not an ideal setup:
- If deps / files change, this will need updating.
- It only breaks on error, not warning.
- It doesn't actually run any package tests.

I haven't gone through all packages either.  Might be worth automating something
like this.

See try-run here:

https://travis-ci.org/dart-lang/sdk/builds/172066040

R=jmesserly@google.com

Committed:
https://github.com/dart-lang/dev_compiler/commit/830cf7c3ea89b870140c71a6d36d...
==========

[vsm, 2016-11-01 13:01:51]

Committed patchset #1 (id:1) manually as
830cf7c3ea89b870140c71a6d36de9f6e3c27d00 (presubmit successful).

[vsm, 2016-11-01 18:21:42]

https://codereview.chromium.org/2465923003/diff/1/pkg/dev_compiler/tool/build...
File pkg/dev_compiler/tool/build_pkgs.sh (right):

https://codereview.chromium.org/2465923003/diff/1/pkg/dev_compiler/tool/build...
pkg/dev_compiler/tool/build_pkgs.sh:12: # Under pkg
On 2016/10/31 23:35:51, Jennifer Messerly wrote:
> should we just enumerate the directory? instead of hard coding

I'm thinking a better way to do this would be to a Dart file that walks over all
packages in pkg/ and third_party/pkg, determines their dependencies (a la
global_compile.dart), and invokes DDC on each package in the right order, with
the right summaries.