When testing, make sure we run Dart from an absolute path.

When testing, make sure we run Dart from an absolute path.

The bots pass in relative paths, which breaks when we run processes
with new working directories.

R=kevmoo@google.com

Committed: https://github.com/dart-lang/test/commit/46e0cc1797e9fef78a4fe7de9c6c39864462a9de

[kevmoo, 2015-04-21 22:53:10]

lgtm

https://codereview.chromium.org/1094533005/diff/1/test/io.dart
File test/io.dart (right):

https://codereview.chromium.org/1094533005/diff/1/test/io.dart#newcode41
test/io.dart:41: // The bots use a relative package root, which we need to make
absolute if
want to make this comment more general than just for our 'bots' – could apply to
anyone using a relative package root, right?

[nweiz, 2015-04-21 22:57:28]

Code review changes

[nweiz, 2015-04-21 22:57:33]

https://codereview.chromium.org/1094533005/diff/1/test/io.dart
File test/io.dart (right):

https://codereview.chromium.org/1094533005/diff/1/test/io.dart#newcode41
test/io.dart:41: // The bots use a relative package root, which we need to make
absolute if
On 2015/04/21 22:53:10, kevmoo wrote:
> want to make this comment more general than just for our 'bots' – could
apply to
> anyone using a relative package root, right?

Done.

[nweiz, 2015-04-21 22:57:49]

Committed patchset #2 (id:20001) manually as
46e0cc1797e9fef78a4fe7de9c6c39864462a9de (presubmit successful).