Update language status file

Update language status file

Add issue numbers.

Change a test to not rely on the toString() value if a TypeError.

R=kustermann@google.com
BUG=

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

[kustermann, 2013-08-27 14:19:26]

LGTM with one question.

https://chromiumcodereview.appspot.com/23599002/diff/1/tests/language/languag...
File tests/language/language_dart2js.status (right):

https://chromiumcodereview.appspot.com/23599002/diff/1/tests/language/languag...
tests/language/language_dart2js.status:68: generic_test: Fail, OK
Why is it 'Fail, OK'?

[Søren Gjesse, 2013-08-28 06:41:22]

https://chromiumcodereview.appspot.com/23599002/diff/1/tests/language/languag...
File tests/language/language_dart2js.status (right):

https://chromiumcodereview.appspot.com/23599002/diff/1/tests/language/languag...
tests/language/language_dart2js.status:68: generic_test: Fail, OK
On 2013/08/27 14:19:26, kustermann wrote:
> Why is it 'Fail, OK'?

This is in the section [ $compiler == dart2js && $unchecked ], and the test only
"works" in checked mode as it catches a TypeError. For the VM the
"VMOptions=--checked" comment is in the test to make work in unchecked mode.

This is the case for most tests in the [ $compiler == dart2js && $unchecked ]
section. I think we should find some way around this as the list of Fail, OK
tests here is problematic.

[Søren Gjesse, 2013-08-28 06:48:42]

Committed patchset #1 manually as r26764 (presubmit successful).