Remove observatory symlink from the repository - they have unforseen issues when copying around stu…

Remove observatory symlink from the repository - they have unforseen issues when copying around stuff for testing.

Long storry short: for testing the ability to do pub get and pub build we copy in the packages and test them if they have a pubspec yaml file.

If you copy a symlink, like the one added in r38788, without -L to cp you will just get the relative symlink copied in, which will, of course, not work.

I generally think it is a bad idea to add symlinks to the repo, we have had enough issues with the ones for packages/pub

Instead, to keep the testing, add the runtime/bin/vmservice to the location of where we look for packages

R=koda@google.com

Committed: https://code.google.com/p/dart/source/detail?r=38983

[ricow1, 2014-08-01 08:21:47]

On 2014/08/01 08:21:08, ricow1 wrote:

As far as I can see there are still no tests in here that will be run

[koda, 2014-08-06 16:21:43]

On 2014/08/01 08:21:47, ricow1 wrote:
> On 2014/08/01 08:21:08, ricow1 wrote:
> 
> As far as I can see there are still no tests in here that will be run

This CL moves the allocations_test from standalone to observatory:
https://codereview.chromium.org/445023003/

[koda, 2014-08-06 16:43:53]

lgtm

[ricow1, 2014-08-07 12:59:41]

Committed patchset #2 manually as r38983 (presubmit successful).

[koda, 2014-08-07 14:02:33]

On 2014/08/07 12:59:41, ricow1 wrote:
> Committed patchset #2 manually as r38983 (presubmit successful).

The pub build bot still doesn't run the test in
runtime/bin/vmservice/client/test.