Adds a simarmv5te build and test target.

Adds a simarmv5te build and test target.

Also:
- Removes command line flags to choose simulated arm version.
  I think we should use build targets instead, like in this change,
  to make building and testing more obvious.
- Skips pkg tests on all simulators.

R=regis@google.com, ricow@google.com

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

[zra, 2015-04-09 20:38:35]

zra@google.com changed reviewers:
+ asiva@google.com, iposva@google.com

[ricow1, 2015-04-10 08:23:40]

ricow@google.com changed reviewers:
+ ricow@google.com

[ricow1, 2015-04-10 08:23:41]

python files and status file changes lgtm

https://codereview.chromium.org/1077823002/diff/20001/runtime/tests/vm/vm.status
File runtime/tests/vm/vm.status (right):

https://codereview.chromium.org/1077823002/diff/20001/runtime/tests/vm/vm.sta...
runtime/tests/vm/vm.status:43: [ $arch == simarm || $arch == simarmv5te || $arch
== simarm64 || $arch == simmips ]
We could add a group marker to config, i.e., you would be able to state
[ $vmsimulator ]  instead here

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py
File tools/build.py (right):

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py#newcode58
tools/build.py:58:
metavar='[all,ia32,x64,simarm,arm,simarmv5te,armv5te,simmips,mips,simarm64,arm64,]',
long line

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py#newcode109
tools/build.py:109: 'mips', 'simarm64', 'arm64',]
I would indent this one less space

https://codereview.chromium.org/1077823002/diff/20001/tools/testing/dart/runt...
File tools/testing/dart/runtime_configuration.dart (right):

https://codereview.chromium.org/1077823002/diff/20001/tools/testing/dart/runt...
tools/testing/dart/runtime_configuration.dart:173: case 'armv5te':
I wonder if we should have an even higher multiplier for this given the speed on
the real hardware devices

[zra, 2015-04-10 16:07:20]

https://codereview.chromium.org/1077823002/diff/20001/runtime/tests/vm/vm.status
File runtime/tests/vm/vm.status (right):

https://codereview.chromium.org/1077823002/diff/20001/runtime/tests/vm/vm.sta...
runtime/tests/vm/vm.status:43: [ $arch == simarm || $arch == simarmv5te || $arch
== simarm64 || $arch == simmips ]
On 2015/04/10 08:23:41, ricow1 wrote:
> We could add a group marker to config, i.e., you would be able to state
> [ $vmsimulator ]  instead here
> 

That would be useful, yah. I think there are a number of places where we
currently list all the simulators to mark tests as Slow, etc.

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py
File tools/build.py (right):

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py#newcode58
tools/build.py:58:
metavar='[all,ia32,x64,simarm,arm,simarmv5te,armv5te,simmips,mips,simarm64,arm64,]',
On 2015/04/10 08:23:41, ricow1 wrote:
> long line

Done.

https://codereview.chromium.org/1077823002/diff/20001/tools/build.py#newcode109
tools/build.py:109: 'mips', 'simarm64', 'arm64',]
On 2015/04/10 08:23:41, ricow1 wrote:
> I would indent this one less space

Done.

https://codereview.chromium.org/1077823002/diff/20001/tools/testing/dart/runt...
File tools/testing/dart/runtime_configuration.dart (right):

https://codereview.chromium.org/1077823002/diff/20001/tools/testing/dart/runt...
tools/testing/dart/runtime_configuration.dart:173: case 'armv5te':
On 2015/04/10 08:23:41, ricow1 wrote:
> I wonder if we should have an even higher multiplier for this given the speed
on
> the real hardware devices

In my initial testing, this timeout seemed to work okay with a small number of
exceptions that I haven't had a chance to investigate, yet.

[zra, 2015-04-15 14:54:16]

ping for VM code review.

[zra, 2015-04-15 19:34:00]

zra@google.com changed reviewers:
+ regis@google.com

[regis, 2015-04-15 20:09:57]

LGTM

[zra, 2015-04-15 20:45:02]

Committed patchset #5 (id:80001) manually as r45181.