Issue 1317. Mark test as failing in release

Mark test as failing in release.
http://code.google.com/p/dart/issues/detail?id=1317


R=mmendez@google.com,zundel@google.com
BUG=
TEST=

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

[zundel, 2012-01-24 16:30:36]

LGTM.

To investigate, I added a 'print()' line after the call to 'string'.contains()
and it printed out.

I've tried going through and understanding why this happens, and all I can think
of is that closure is doing some kind of optimization.  There is no explicit
null check, so possibly closure, knowing that pattern is NULL inadvertently
avoids the NULL pointer reference.

[mmendez, 2012-01-24 19:12:33]

FWIW, it might be worth it to look at the cllosure optimized code with the human
readable flag turned on, if that has not been done already.

On 2012/01/24 16:30:36, zundel wrote:
> LGTM.
> 
> To investigate, I added a 'print()' line after the call to 'string'.contains()
> and it printed out.
> 
> I've tried going through and understanding why this happens, and all I can
think
> of is that closure is doing some kind of optimization.  There is no explicit
> null check, so possibly closure, knowing that pattern is NULL inadvertently
> avoids the NULL pointer reference.