Status file update after adding new vm-linux-release-optcounter-threshold builder

Status file update after adding new vm-linux-release-optcounter-threshold builder

TBR=ricow@google.com

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

[kustermann, 2013-09-24 12:19:19]

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

[ricow1, 2013-09-24 12:20:21]

LGTM

https://codereview.chromium.org/23710088/diff/1/tests/co19/co19-runtime.status
File tests/co19/co19-runtime.status (right):

https://codereview.chromium.org/23710088/diff/1/tests/co19/co19-runtime.statu...
tests/co19/co19-runtime.status:153: LibTest/typed_data/Float32x4/clamp_A01_t01:
Pass, Fail # Issue 13543
are they really flaky, I saw those consistently fail on my machine a few days
back

[Florian Schneider, 2013-09-24 12:25:58]

On 2013/09/24 12:19:19, kustermann wrote:
> Committed patchset #1 manually as r27815 (presubmit successful).

LGTM. Thanks!

[kustermann, 2013-09-24 12:36:27]

https://codereview.chromium.org/23710088/diff/1/tests/co19/co19-runtime.status
File tests/co19/co19-runtime.status (right):

https://codereview.chromium.org/23710088/diff/1/tests/co19/co19-runtime.statu...
tests/co19/co19-runtime.status:153: LibTest/typed_data/Float32x4/clamp_A01_t01:
Pass, Fail # Issue 13543
On 2013/09/24 12:20:22, ricow1 wrote:
> are they really flaky, I saw those consistently fail on my machine a few days
> back

They started to fail on my machine after enabling the optimization threshold.
=> We can't determine in a status file if we've set the low optimization counter
threshold or not, so we *need* to mark them as flaky.