bug on multi-test with multiple components

[sigmundch]

test.dart has a special meaning for a multitest when the type of error is 'runtime error':

mytest.dart:
 ...
 ... /// 01: runtime error

Because dartc doesn't run the code anymore, this is not a negative test. For the vm, and any other component it is a negative test. More precisely, see test.dart line 149:
  bool isNegative = (outcome.contains('compile-time error')
      || (outcome.contains('runtime error') && (component != 'dartc')))

However, multi-tests are defined once, so while the following two calls pass all tests:
 ./tools/test.py -m release -c vm language/CodeAfterTryIsExecutedTest
 ./tools/test.py -m release -c dartc language/CodeAfterTryIsExecutedTest

Testing the vm and dartc together makes it fail:
 ./tools/test.py -m release -c vm,dartc language/CodeAfterTryIsExecutedTest
FAILED: dartc release_ia32 language/CodeAfterTryIsExecutedTest/01
Expected: pass
Actual: fail

Command line: out/Release_ia32/compiler/bin/dartc_test --ignore-unrecognized-flags out/Release_ia32/generated_tests/language/CodeAfterTryIsExecutedTest_01.dart

[DartBot]

This comment was originally written by ngeoffray@google.com

---

Thanks Siggi for the bug report, and finding where the problem was. I'll follow up with a CL.

---

cc @peter-ahe-google.
Set owner to ngeoffray@google.com.
Added Started label.

[DartBot]

This comment was originally written by ngeoffray@google.com

---

Should be fixed in https://chromiumcodereview.appspot.com/9466008.

---

Added Fixed label.