Enable language tests on SIMARM and mark 14 of them as failing.

tests/language/language.status

Index: tests/language/language.status
===================================================================
--- tests/language/language.status	(revision 23447)
+++ tests/language/language.status	(working copy)
@@ -801,9 +801,25 @@
 type_variable_scope_test/05: fail
 
 
-[ $arch == simarm ]
+[ $arch == arm ]
 *: Skip

[kustermann, 2013/06/03 07:54:26]

Why do you skip all language tests on arm?
I setup a new builder on FYI which builds and runs arm tests on real hardware.
Now it's not doing anything, because you skip all the tests on arm.
What is the reason for that?

[zra, 2013/06/03 15:30:52]

I think this was probably a misunderstanding. The stuff from simarm below should
probably be copied up here to the arm section.

[kustermann, 2013/06/03 15:40:39]

In case this was an accident: There a couple of other status files where arm
tests were marked as skip (we don't run any tests at the moment). You might want
to update these as well.

I don't know what your plans are, but if you enable all the tests on arm and
update the status files for failing/crashing tests we could move the arm board
builder from FYI to the main waterfall.

 
+[ $arch == simarm ]
+arithmetic_test: Crash
+bit_operations_test: Crash
+char_escape_test: Pass, Crash
+deopt_smi_op_test: Fail
+div_with_power_of_two_test: Fail
+double_modulo_test: Crash
+gc_test: Crash
+invocation_mirror_test: Fail
+large_implicit_getter_test: Crash
+load_to_load_forwarding_test: Fail
+math_vm_test: Crash
+named_parameters_with_conversions_test: Pass, Crash
+stack_overflow_stacktrace_test: Crash
+stack_overflow_test: Crash
+
 [ $arch == mips ]
 *: Skip