Add new failures to status files, assign issues.

Add new failures to status files, assign issues.

BUG=dartbug.com/18113
R=ricow@google.com

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

[ricow1, 2014-04-09 08:10:56]

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status
File tests/corelib/corelib.status (right):

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status...
tests/corelib/corelib.status:130: string_case_test/02: Fail, OK  # Bug in
Chrome.  Please file issue.
did we? Who is that comment for?

[ricow1, 2014-04-09 08:11:08]

and LGTM, thanks

[Bill Hesse, 2014-04-09 08:29:49]

On 2014/04/09 08:10:56, ricow1 wrote:
> https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status
> File tests/corelib/corelib.status (right):
> 
>
https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status...
> tests/corelib/corelib.status:130: string_case_test/02: Fail, OK  # Bug in
> Chrome.  Please file issue.
> did we? Who is that comment for?

lrn.  There should be an issue for the nearby lines as well.

[Bill Hesse, 2014-04-09 08:30:38]

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

[Lasse Reichstein Nielsen, 2014-04-09 08:54:44]

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status
File tests/corelib/corelib.status (right):

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status...
tests/corelib/corelib.status:130: string_case_test/02: Fail, OK  # Bug in
Chrome.  Please file issue.
This is a bug in v8, and I thought it already had an issue. I can't find it
right now. I'll check with a V8-dev to see if whether I'm going blind or senile.

[Lasse Reichstein Nielsen, 2014-04-09 08:57:04]

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status
File tests/corelib/corelib.status (right):

https://codereview.chromium.org/230163003/diff/1/tests/corelib/corelib.status...
tests/corelib/corelib.status:130: string_case_test/02: Fail, OK  # Bug in
Chrome.  Please file issue.
This could probably be combined with the ($runtime == d8 || $runtome == drt)
above.
For some reason dartium runs a different, older, version of v8.

[Lasse Reichstein Nielsen, 2014-04-09 09:21:36]

Neither blind, nor senile - the bug was in the chromium tracker, not the v8 one.
The issue was fixed in v8 r20197, but apparently hasn't reached the v8 versions
that we use yet.

[ricow1, 2014-04-09 09:28:55]

On 2014/04/09 09:21:36, Lasse Reichstein Nielsen wrote:
> Neither blind, nor senile - the bug was in the chromium tracker, not the v8
one.
> The issue was fixed in v8 r20197, but apparently hasn't reached the v8
versions
> that we use yet.

Do you have a link, it would be nice to annotate the line in the status file
with the issue number