Now that users in general have a reason to disable this, they should
know it exists.

R=rnystrom@google.com

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

R=rnystrom@google.com

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

Now that Platform.resolvedExecutable exists, the environment variable
only provided a way to load files from the wrong SDK.

Closes #1288

R=rnystrom@google.com

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

R=rnystrom@google.com

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

The git invocations in the snapshot-generation code became very flaky
when run in massive parallel via the new test runner. Now a snapshot
will be used if it's manually-generated, and otherwise pub will be run
from source.

R=rnystrom@google.com

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

Fix for pub crashing in checked mode

R=nweiz@google.com

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

As per #1283, this makes it easier to script pub, since it's now
programattically clear whether publishing went through (or, if using
--dry-run, whether validation succeeded).

Closes #1283

R=rnystrom@google.com

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

We moved this location again to get custom pub testing

R=nweiz@google.com
BUG=

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

If all packages depended on by an executable don't use transformers,
this will avoid loading barback entirely and instead run the VM against
the Dart files on the filesystem.

This shaves about 600ms off the load time for "pub run test" when running from
source.

R=rnystrom@google.com

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

These tests broke when removing compatibility with the old "pub run"
behavior.

R=rnystrom@google.com

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

Closes #1235.

R=rnystrom@google.com

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

When I originally wrote this code, I hadn't thought about running tests
from within the Dart repo itself, so the snapshotting logic didn't
work for that case.

R=rnystrom@google.com

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

R=rnystrom@google.com

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

This should fix the analyzer buildbot (see http://build.chromium.org/p/client.dart/builders/analyzer_experimental-linux-release-be/builds/1826/steps/tests%20--host-checked%20--checked/logs/stdio)

R=nweiz@google.com

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

These issues were hidden last time I was testing because I couldn't
actually bring in pub via DEPS.

R=rnystrom@google.com

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

I hadn't considered the case of running tests from within the Dart repo,
but now the package-loading and SDK-detection logic works in that
scenario as well.

R=rnystrom@google.com

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

R=rnystrom@google.com

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

BUG=

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

- Update error string comparison in pub.

BUG=

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

BUG=dartbug.com/23505
Rebase of https://codereview.chromium.org/1035853003/

R=nweiz@google.com

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

This was happening for the most part, but the dependency computer could
get tripped up when a package used a transformer from a dev dependency
on only private files.

R=rnystrom@google.com
BUG= http://dartbug.com/23480

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

The solver was choking when pub's implicit dependencies on barback
failed and had to be backtracked.

R=rnystrom@google.com
TBR

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

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

When running from the pub repo, dart2js needs to see SDK sources that
match up with its own version. compiler_unsupported contains its own
copy of the SDK for exactly this purpose; this CL loads SDK sources from
that copy when running tests from the pub repo.

R=rnystrom@google.com

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

It turns out this variable already existed, with slightly different
semantics. Everything has now been updated, so "runningAsTest" means
running in a test file and "runningFromTest" means running in pub called
by a test file.

R=rnystrom@google.com

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

R=rnystrom@google.com

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

R=rnystrom@google.com

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

Instead of looking in the repo's third party deps, this uses the
packages installed for pub in the package cache. Archived versions of
barback and source_maps are included via Git submodules.

R=rnystrom@google.com

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

R=rnystrom@google.com

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

R=rnystrom@google.com

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

R=rnystrom@google.com

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

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

The idea of this change is to eagerly check, before selecting a package version,
whether that version is compatible with the existing dependencies. This avoids a
bunch of unnecessary backtracking, and makes the progression of the solver more
comprehensible when

R=rnystrom@google.com
BUG= dartbug.com/17429

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

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

`pub serve` used to bind its admin port to the port below the main port. For example `pub serve --port=8081` would automatically bind its admin port to 8080.
With this change the admin server is only started if an --admin-port flag was provided.

BUG= http://dartbug.com/20922
R=rnystrom@google.com

Committed: https://code.google.com/p/dart/source/detail?r=45614
Reverted: https://code.google.com/p/dart/source/detail?r=45633

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

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

This reverts commit 45614

Causes redness on the bots, floitsch@ will investigate offline

R=floitsch@google.com
BUG=

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

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

Also fix an analysis hint.

R=rnystrom@google.com

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

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