ElementLocator first-steps.

The basic shape of the upcomming service with test jig.

For consideration:

  * source location
  * method/class names
Review URL: https://codereview.chromium.org//12382027

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19261 260f80e4-7a28-3924-810f-c04153c831b5
Make oauth2 warning-clean.

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19262 260f80e4-7a28-3924-810f-c04153c831b5
Fix the pkg/http multipart test to avoid a race condition.

BUG=8843

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19263 260f80e4-7a28-3924-810f-c04153c831b5
Make use of Completer.isComplete in pub and pkg/scheduled_test.

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19264 260f80e4-7a28-3924-810f-c04153c831b5
Make pub warning-clean.

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19265 260f80e4-7a28-3924-810f-c04153c831b5
Remove the wrapStream workaround for issue 8310.

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19266 260f80e4-7a28-3924-810f-c04153c831b5
Do not inline List factory if a non-constant argument is passed in order to prevent non-optimal code being generated. This is a temporary fix until we have found a better solution (maybe introduce a high-performance ? operator once its definition settles).
Review URL: https://codereview.chromium.org//12377032

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19267 260f80e4-7a28-3924-810f-c04153c831b5
Speeding up Node.nodes.addAll

During profiling of the Dart API app I noticed quite a non-trivial amount of time and garbage in nodes.addAll. This case can be optimized for the case where we know that both lists are node lists.

BUG=

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19268 260f80e4-7a28-3924-810f-c04153c831b5
When we have excess callbacks, throw instead of calling error() so that we
get a stack trace.
Clean up SpreadArgsHelper.
We can now specify a min and max count for callbacks.
Split onTestResult into two - onTestResult and onTestResultChanged. The
first one is called initially, and the second if further callbacks occur 
after the test was considered complete, or if teardown fails.

See https://code.google.com/p/dart/issues/detail?id=8660
Review URL: https://codereview.chromium.org//12366004

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19269 260f80e4-7a28-3924-810f-c04153c831b5
Don't use package: imports in logging until dartdoc/mirros support them.

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19270 260f80e4-7a28-3924-810f-c04153c831b5
Disable breaking tests while I investigate the issue. I don't really want to revert;
I want to understand this as it may indicate some other problem.
Review URL: https://codereview.chromium.org//12387033

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19271 260f80e4-7a28-3924-810f-c04153c831b5
Fix stack frame index numbers for full stack traces

It used to be:
#0      getCurrentStackTrace (file:///tmp/junk.dart:3:5)
#0      func1 (file:///tmp/junk.dart:10:29)
#1      func2 (file:///tmp/junk.dart:14:8)
#2      func3 (file:///tmp/junk.dart:18:8)
#3      func4 (file:///tmp/junk.dart:22:8)
#4      main (file:///tmp/junk.dart:26:8)
(Notice the two #0 frames on top).

Now it will print this as:
#0      getCurrentStackTrace (file:///tmp/junk.dart:3:5)
#1      func1 (file:///tmp/junk.dart:10:29)
#2      func2 (file:///tmp/junk.dart:14:8)
#3      func3 (file:///tmp/junk.dart:18:8)
#4      func4 (file:///tmp/junk.dart:22:8)
#5      main (file:///tmp/junk.dart:26:8)
Review URL: https://codereview.chromium.org//12381030

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19272 260f80e4-7a28-3924-810f-c04153c831b5
DEPS AutoUpdate: webkit to 1115 (2013-03-01 10:55:09 +0400) ager@google.com
Remove HTMLOutputElementCustom which is no longer needed.
http://src.chromium.org/viewvc/multivm/trunk/webkit?view=rev&revision=1115

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19273 260f80e4-7a28-3924-810f-c04153c831b5
Get rid of the custom union/intersection methods on the potential primitive array type in preparation of getting rid of the type completely.

R=ngeoffray@google.com
BUG=

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

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

The test standalone/io/https_client_test does not exist any more

The test standalone/io/web_socket_test can still fail on Windows

The test standalone/io/http_content_length_test is seen failing
on Windows

The rest is re-organizing the order.

TBR=ajohnsen@google.com

BUG=

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19275 260f80e4-7a28-3924-810f-c04153c831b5
Remove wrong type annotation

nativeCreateConnect returns either a bool (only true) or an OSError.

TBR=ajohnsen@google.com

BUG=

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19276 260f80e4-7a28-3924-810f-c04153c831b5
Add exception information to help diagnose issue 8865

Might we be getting a SocketIOException? If soshould it be wrapped in a HttpException?

TBR=ajohnsen@google.com

BUG=https://code.google.com/p/dart/issues/detail?id=8865

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

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

Remove flaky marker for test io/http_content_length_test on Windows to
get the actual error message in the log file

TBR=ajohnsen@google.com
BUG=https://code.google.com/p/dart/issues/detail?id=8865

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

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

R=ricow@google.com
BUG=

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

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge@19279 260f80e4-7a28-3924-810f-c04153c831b5
Mark --disallow-unsafe-eval as a supported feature in usage description.

R=ahe@google.com
BUG=

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

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