Add mips failures to status files.

runtime/tests/vm/vm.status

Index: runtime/tests/vm/vm.status
diff --git a/runtime/tests/vm/vm.status b/runtime/tests/vm/vm.status
index 72e60222144053f901e2c9d659ba20fcb5f8c137..6276e55fb352f22c9cc4c8ce10e208772684a845 100644
--- a/runtime/tests/vm/vm.status
+++ b/runtime/tests/vm/vm.status
@@ -70,7 +70,10 @@ dart/inline_stack_frame_test: RuntimeError
 [ $arch == mips ]
 cc/Cop1CvtDL: Crash # Illegal instructions
 cc/Cop1CvtDL_neg: Crash # Illegal instructions
-cc/StaticNonNullSumCallCodegen: Crash # dartbug.com/17440
+cc/StaticNonNullSumCallCodegen: Crash, Pass # dartbug.com/17440

[kustermann, 2014/03/18 16:10:12]

Is this really flaky or is it a difference between release/debug?

[Bill Hesse, 2014/03/18 16:21:27]

It is really flaky on debug.  On release we have only seen crash.

+
+[ $arch == mips && $mode == debug ]
+cc/FindCodeObject: Skip # Takes more than 8 minutes, times out.

[kustermann, 2014/03/18 16:10:12]

Why should this take 8 minutes?

Please add the issue number of the "mips triaging bug" here.

[Bill Hesse, 2014/03/18 16:21:27]

It takes 1 minute in release mode.  On sim-mips it is really fast, and on intel.
 Added the triage issue.

 
 [ $compiler == none && ($runtime == drt || $runtime == dartium) ]
 dart/mirrored_compilation_error_test: Skip # Can't pass needed VM flag