Use gnueabihf for ARM + enabled corelib/isolate/lib/standalone tests on ARM again

Use gnueabihf for ARM + enabled corelib/isolate/lib/standalone tests on ARM again

R=regis@google.com

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

[regis, 2013-06-11 13:09:14]

LGTM

https://codereview.chromium.org/16638009/diff/2001/tests/corelib/corelib.status
File tests/corelib/corelib.status (right):

https://codereview.chromium.org/16638009/diff/2001/tests/corelib/corelib.stat...
tests/corelib/corelib.status:108: *: Skip
If these tests pass on ARM hardware, they should also pass on the simulator, or
the failing ones should be identified, but not skipped.

https://codereview.chromium.org/16638009/diff/2001/tests/isolate/isolate.status
File tests/isolate/isolate.status (right):

https://codereview.chromium.org/16638009/diff/2001/tests/isolate/isolate.stat...
tests/isolate/isolate.status:142: *: Skip
ditto

https://codereview.chromium.org/16638009/diff/2001/tests/lib/lib.status
File tests/lib/lib.status (right):

https://codereview.chromium.org/16638009/diff/2001/tests/lib/lib.status#newco...
tests/lib/lib.status:113: *: Skip
ditto

https://codereview.chromium.org/16638009/diff/2001/tests/standalone/standalon...
File tests/standalone/standalone.status (right):

https://codereview.chromium.org/16638009/diff/2001/tests/standalone/standalon...
tests/standalone/standalone.status:163: *: Skip
ditto

[kustermann, 2013-06-11 14:21:37]

https://codereview.chromium.org/16638009/diff/2001/tests/corelib/corelib.status
File tests/corelib/corelib.status (right):

https://codereview.chromium.org/16638009/diff/2001/tests/corelib/corelib.stat...
tests/corelib/corelib.status:108: *: Skip
On 2013/06/11 13:09:14, regis wrote:
> If these tests pass on ARM hardware, they should also pass on the simulator,
or
> the failing ones should be identified, but not skipped.

They probably don't pass. But we will never find out whether they pass or not if
we never run them.

The procedure should be like this:
- enable all tests
- run them and triage the failures
- file a bug for each failure group and update the corresponding status file
(with the bug number as a comment)
- once the issue has been fixed, close the bug and remove the suppression in the
status file

If you want I can remove the SKIP markers for simarm as well, but I'll do it in
a separate CL with status file updates and bugs entries. (Or one of you does
it?)

[kustermann, 2013-06-11 14:21:44]

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