Adding test for old wrappers causing multiple upgrades

Adding test for old wrappers causing multiple upgrades

This is the test for https://codereview.chromium.org/54833003/

BUG=
R=vsm@google.com

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

[blois, 2013-10-31 18:43:13]

https://codereview.chromium.org/55153002/diff/30001/tests/html/custom/templat...
File tests/html/custom/template_wrappers_test.dart (right):

https://codereview.chromium.org/55153002/diff/30001/tests/html/custom/templat...
tests/html/custom/template_wrappers_test.dart:77: var M = 100;
Bumping down to 100 makes this quite a bit faster and I'm still repro'ing the
behavior. Tests are currently flaky/timing out on bots.

Would be much better if we had a way to force GC.

[vsm, 2013-10-31 19:30:43]

lgtm - siva is there a better pattern to force a gc from dart?  this might not
actually test anything if we change the heap size or even the underlying gc.

[siva, 2013-10-31 19:49:05]

https://codereview.chromium.org/55153002/diff/30001/tests/html/custom/templat...
File tests/html/custom/template_wrappers_test.dart (right):

https://codereview.chromium.org/55153002/diff/30001/tests/html/custom/templat...
tests/html/custom/template_wrappers_test.dart:77: var M = 100;
This seems like a very contrived way to trigger a GC.
The vm has an option --gc_at_alloc which forces a GC on every allocation. We
should see if there is a way to run this test with that additional option turned
on.

In standalone VM we have a mechanism which allows us to add an
option for a test, e.g:

// Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

// VMOptions=--throw_on_javascript_int_overflow


import "package:expect/expect.dart";

int literals() {
  var okay_literal = 0x20000000000000;
  var too_big_literal = 0x20000000000001;  /// 01: compile-time error
  return okay_literal;
}

main() {
  Expect.equals(0x20000000000000, literals());
}

I don't know if this works when run inside dartium or not.



On 2013/10/31 18:43:13, blois wrote:
> Bumping down to 100 makes this quite a bit faster and I'm still repro'ing the
> behavior. Tests are currently flaky/timing out on bots.
> 
> Would be much better if we had a way to force GC.

[blois, 2013-10-31 20:20:53]

I opened bug 14689 to investigate getting this working in Dartium- I don't think
it's blocking for this release.

The current approach is definitely hacky, but won't generate false failures.

[blois, 2013-10-31 21:16:31]

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