FYI, you can run the transformer unit tests via gulp test.unit.dartvm. Travis failed because some of them are failing...

Also, regarding the failures in the jobs typescript_next and dart_dev: These are because Typescript and Dart have more checks now. Rebase this PR ontop of my PR #8680 which contains fixes to these and which I will land ASAP.

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

Thanks @tbosch !
Fixed Dart test expectations + rebased onto tbosch/fix_types, but still getting a weird failure (same as in your PR) on typescript_next:

[15:31:33] Error: [DiffingTSCompiler]: Typescript found the following errors:
  /home/travis/build/angular/angular/node_modules/typescript/lib/lib.d.ts (883, 5): Duplicate identifier 'stack'.
  /home/travis/build/angular/angular/tmp/diffing_plugin_wrapper-output_path-TaBpImXX.tmp/angular2/typings/node/node.d.ts (13, 5):

Yes, just found it in my PR as well. Please rebase again :-)

(I.e. I deactivated the typescript_next build, as we don't need it to sync into G3)

CLAs look good, thanks!

Ok, I finally landed everything to make g3_master green again and synced into g3.
Could you rebase again? Sorry that this takes so long, but we had accumulated a bit of technical dept...

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

CLAs look good, thanks!

Rebased :-)

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}