Use write instead of writeln for client/server communication.

We have observed that each string sent from the server to the client
using stdout.write() takes at least one cycle of the event loop to
complete.  Since writeln() is implemented using two calls to write(),
this means that streaming of messages to the client was almost always
falling behind the actual rate of analysis, resulting in very annoying
delays for the user.

As a stopgap, send each message from server to client using a single
call to write().  This doesn't completely solve the problem, but it
should reduce its impact while we work on a better solution.

R=scheglov@google.com

Review URL: https://codereview.chromium.org//757013002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41959 260f80e4-7a28-3924-810f-c04153c831b5
Add android device id to test output for failing tests.

BUG=
R=kustermann@google.com

Review URL: https://codereview.chromium.org//755263002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41960 260f80e4-7a28-3924-810f-c04153c831b5
During resolution, record the target of break/continue statements.

This adds a new "target" field to BreakStatement and ContinueStatement
which points to the AST for the statement that the break/continue is
breaking from or continuing to.  For labeled break and continue
statements, this will always be the statement identified by the label
(not the LabeledStatement itself but its child).  For unlabeled break
and continue statements, this will be the innermost enclosing loop (or
switch statement, for break statements), provided that it is not in an
enclosing function.

R=brianwilkerson@google.com

Review URL: https://codereview.chromium.org//725473005

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41961 260f80e4-7a28-3924-810f-c04153c831b5
Fix parsing of awaitable expressions with nested functions

“have seen await” flag must be properly saved and restored when
parsing nested function (literals) inside an await expression.

Fixes issue 21536

R=srdjan@google.com

Review URL: https://codereview.chromium.org//755053002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41962 260f80e4-7a28-3924-810f-c04153c831b5
Fix test expectations

Review URL: https://codereview.chromium.org//758133002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41963 260f80e4-7a28-3924-810f-c04153c831b5
Bump multivm DEPS

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41964 260f80e4-7a28-3924-810f-c04153c831b5
Clean up resolution of unlabeled break/continue targets.

Move the tracking of unlabeled break and continue targets from
ResolverVisitor to ScopedVisitor, where it makes more sense, and add a
new ImplicitLabelScope class that encapsulates the logic for it.

R=brianwilkerson@google.com

Review URL: https://codereview.chromium.org//758103002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41965 260f80e4-7a28-3924-810f-c04153c831b5
Update errors during incremental resolution.

Update offsets for the existing ones, remove some of them, add new.

R=brianwilkerson@google.com
BUG=

Review URL: https://codereview.chromium.org//757743004

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@41966 260f80e4-7a28-3924-810f-c04153c831b5