Make the apply.js unit test more resilient to differing stack positions....

Make the apply.js unit test more resilient to differing stack positions.

More information is at http://code.google.com/p/v8/issues/detail?id=742


Committed: http://code.google.com/p/v8/source/detail?r=4918

[zarko, 2010-06-21 23:51:10]

I think this change should fix the problem with this test on OS X. (The problem
also happens to surface on other platforms in the isolates branch, which is why
I'm particularly interested in seeing the issue settled.)

Thanks
  Luke

[Erik Corry, 2010-06-22 10:21:38]

LGTM

[Vitaly Repeshko, 2010-06-22 12:58:32]

LGTM

test/mjsunit/mjsunit.status should be updated to enable the test.

http://codereview.chromium.org/2835014/diff/1/2
File test/mjsunit/apply.js (right):

http://codereview.chromium.org/2835014/diff/1/2#newcode115
test/mjsunit/apply.js:115: var stack_corner_case_failure = 0;
Use boolean?

[zarko, 2010-06-22 21:48:20]

Just want to make sure that I'm doing this correctly.

Thanks
  Luke

http://codereview.chromium.org/2835014/diff/5001/6002
File test/mjsunit/mjsunit.status (left):

http://codereview.chromium.org/2835014/diff/5001/6002#oldcode39
test/mjsunit/mjsunit.status:39: 
Is this sufficient to re-enable the test?

[Vitaly Repeshko, 2010-06-22 22:01:46]

http://codereview.chromium.org/2835014/diff/5001/6002
File test/mjsunit/mjsunit.status (left):

http://codereview.chromium.org/2835014/diff/5001/6002#oldcode39
test/mjsunit/mjsunit.status:39: 
On 2010/06/22 21:48:20, zarko wrote:
> Is this sufficient to re-enable the test?

I think so, yes. After submitting you can check status at
http://build.chromium.org/buildbot/v8/waterfall. Please also update the bugs.