Without strong mode, a "good enough" implementation is to simply call
the generic method with "dynamic" for the type arguments, which is what
this does. That should be enough to unblock our internal users.
We also need to not report a compile error when
dart_internal/extract_type_arguments.dart imports the hidden
"dart:_internal" library.
This patch does both of those for the VM and dart2js (using its old
front end).
Note that the test still fails because the test is more particular than
most actual user code would be -- it validates that the instantiated
type arguments are *exactly* correct, and not that the returned object
is merely subtype compatible.
Bug:
Change-Id: I0343beace4991861b29712b3fd7067ec8dc8f8ba
Reviewed-on: https://dart-review.googlesource.com/28020
Commit-Queue: Bob Nystrom <rnystrom@google.com>
Reviewed-by: Alexander Thomas <athom@google.com>
Reviewed-by: Régis Crelier <regis@google.com>
Reviewed-by: Sigmund Cherem <sigmund@google.com>
Switch it to use pkg/vm/tool/dart2 which is the source of truth for what
Dart 2 VM configuration means. Don't pass any additional flags from
tools/test.py itself.
Align pkg/vm/tool/dart2 with what tools/test.py was passing to VM on _2 suites.
Make default invocation `tools/test.py -c dartk --strong -m release,debug`
green by updating status files and skipping suites that are not Dart 2.0
compliant. I have filed issues #31588 for isolate suite and #31587 for
service suite.
Reland of https://dart-review.googlesource.com/27820
Change-Id: I49400fae716f75425e70bf1e561b3375ba39157e
Reviewed-on: https://dart-review.googlesource.com/28565
Commit-Queue: Vyacheslav Egorov <vegorov@google.com>
Reviewed-by: Martin Kustermann <kustermann@google.com>
Some of these are data files that weren't picked up by the migration
script. Some are files that slipped between blocks of tests.
Change-Id: I184dc4701758b280444d54ec55c225ade30f3276
Reviewed-on: https://dart-review.googlesource.com/26423
Reviewed-by: Emily Fortuna <efortuna@google.com>
Commit-Queue: Bob Nystrom <rnystrom@google.com>
Switch it to use pkg/vm/tool/dart2 which is the source of truth for what
Dart 2 VM configuration means. Don't pass any additional flags from
tools/test.py itself.
Align pkg/vm/tool/dart2 with what tools/test.py was passing to VM on _2 suites.
Make default invocation `tools/test.py -c dartk --strong -m release,debug`
green by updating status files and skipping suites that are not Dart 2.0
compliant. I have filed issues #31588 for isolate suite and #31587 for
service suite.
Change-Id: I882b28f6a011eabf69c349ff0792b275434e39ff
Reviewed-on: https://dart-review.googlesource.com/27820
Commit-Queue: Vyacheslav Egorov <vegorov@google.com>
Reviewed-by: Alexander Markov <alexmarkov@google.com>
Reviewed-by: Siva Annamalai <asiva@google.com>
Reviewed-by: Martin Kustermann <kustermann@google.com>
The bot names are picked from the platform selected. The tool now also ask for xvfb if on linux.
Bug:
Change-Id: I47dd28a0240f34607535808326a182bf663ead04
Reviewed-on: https://dart-review.googlesource.com/24821
Reviewed-by: Alexander Thomas <athom@google.com>
This small utility program makes it easier to invoke custom steps on try
builders.
Bug:
Change-Id: I63d3d77365f47d79f489a70fef5431a93a6663e5
Reviewed-on: https://dart-review.googlesource.com/24440
Reviewed-by: Alexander Thomas <athom@google.com>
This just makes the name more appropriate since now that the default incremental
generator is not using kernel-driver altogether.
Change-Id: Ic7357dbb4eaad482f20249dd13ba3a49a39322d3
Reviewed-on: https://dart-review.googlesource.com/22160
Commit-Queue: Sigmund Cherem <sigmund@google.com>
Reviewed-by: Jonas Termansen <sortie@google.com>
This lets us benchmark separately:
- IKG implementations (the default based on kernel-driver or the minimal implementation)
- strong and non-strong mode
This also adds commands to try_benchmarks that highlight how these options will be used.
Change-Id: I5ce2c4563b7e79c33d78df7fd87be76f5d47e3f4
Reviewed-on: https://dart-review.googlesource.com/21320
Reviewed-by: Jonas Termansen <sortie@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Sigmund Cherem <sigmund@google.com>
This bot catches whenever benchmarks would break. By putting this bot in
the commit queue, we can avoid many kinds of benchmark breakage that would
otherwise require bothersome triaging and cleaning up after the fact.
This bot has been tested and runs in 21-27 minutes.
Change-Id: I0fc08425094b32cf77d5f1a2ed840ad1bb11aedf
Reviewed-on: https://dart-review.googlesource.com/19940
Commit-Queue: Jonas Termansen <sortie@google.com>
Reviewed-by: Alexander Thomas <athom@google.com>
Reviewed-by: Morten Krogh-jespersen <mkroghj@google.com>
The original builder was sharded and ran both normal and checked tests. It
always took around 1 hour and 45 minutes to run.
The builder has been split up into two, one running normal and one running
checked tests and unit test.
The builder dart2js-hostchecked-checked-linux-ia32-d8 should be added to luci.
Bug:
Change-Id: I7fc3045aa6fc0b2e6927e3a3092396339da6e9b3
Reviewed-on: https://dart-review.googlesource.com/17787
Reviewed-by: Alexander Thomas <athom@google.com>
Note that the current recipe runs strong libraries, which I think is no longer
in use and also runs the same unit tests (not in strong mode) as the non-strong
builders. Is that an error or?
Bug:
Change-Id: Ia573747ed00bac617995844be757ebbdb325874e
Reviewed-on: https://dart-review.googlesource.com/18544
Reviewed-by: Alexander Thomas <athom@google.com>
Jenny Messerly