Deleted http_resource_test – the associated classes no longer exist
Deleted int_fromEnvironment3 - validated type semantics
Tweaked hash_set_type_check – made it very simple.
Also tweaked some analyzer hints
R=rnystrom@google.com
Review-Url: https://codereview.chromium.org/2990623002 .
Another fairly simple block. regress-standalone required the
introduction of two seperate result variables as result was having two
different types assigned to it at different times.
BUG=
R=rnystrom@google.com
Review-Url: https://codereview.chromium.org/2985823002 .
Unusual things in this block:
- This is my first attempt to fix a multitest with various errors in it,
double_parse_test.dart. Most of them revolve around multitest #01 and
the conflict it has with the new multitest #04.
BUG=
R=rnystrom@google.com
Review-Url: https://codereview.chromium.org/2988573002 .
This also:
- replaces --use-kernel with --use-kernel-in-ssa
- replaces --load-dill with --use-kernel
- makes --use-kernel support both: compiling from .dill or from .dart
- change the default of other options that are currently disabled when --use-kernel is on.
- adds .status lines for all tests in language/corelib/dart2js_extra/dart2js_native
R=efortuna@google.com
Note: this CL is built on top of another change
(https://codereview.chromium.org/2981403002/) that adds preview_dart_2 to
test.dart
Review-Url: https://codereview.chromium.org/2989453002 .
Unusual things in this block:
- date_time10_test.dart had no strong mode fork, and reveals what looks
like a legit DDC bug at first glance. Excluded it for now in the status file.
- date_time_test.dart had small differences between the two forks that looked
like an error. Fixed.
BUG=
R=bkonyi@google.com, rnystrom@google.com
Review-Url: https://codereview.chromium.org/2984063002 .
-Spit string_test into string_test and string_static_test
-Added various MissingCompileTimeError entries in status files for
tests which throw exceptions on configurations that haven't implemented Dart 2.0
-Switched var -> dynamic in symbol_operator_test
BUG=
R=jcollins@google.com, rnystrom@google.com
Review-Url: https://codereview.chromium.org/2983253002 .
Unusual things in this block:
- corelib_strong/data_uri_test.dart was behind corelib, so migrated
that file from corelib.
- core_runtime_types_test was split per the document into static
and non-static versions
- data_resource_test.dart is now pointless since class Resource
was moved from dart:core to http://github.com/dart-lang/resource,
so deleted.
BUG=
R=rnystrom@google.com
Review-Url: https://codereview.chromium.org/2986503002 .
This change makes big_integer_arith_vm_test strong-mode compatible, and allows
dartdevc/dart2js to build and run big_integer tests where they can.
New issue 30170 filed to track DDC big integer handling.
BUG=
R=rnystrom@google.com
Review-Url: https://codereview.chromium.org/2978013002 .
Revert "Precompiler doesn't report Dart 2.0 static type errors yet."
This reverts commit 7af2d86ed3.
Revert "Move absstract_exact_selector back into the language tests. (#30169)"
This reverts commit 452d2d0840.
Revert "Set up directories for migrated Dart 2.0 tests and migrate a couple. (#30149)"
This reverts commit 47985d6dbd.
R=zra@google.com
BUG:dartbug.com/30171
Review-Url: https://codereview.chromium.org/2979073002 .
* Set up directories for migrated Dart 2.0 tests and migrate a couple.
- Create new "_2" directories where tests that have been validated as
ready for Dart 2.0 will end up.
- Create empty status files for each directory.
- Add those directories to the set of default selectors you get when you
run test.py. This gets the VM bots running them.
- Get the DDC bots running those suites.
- Move abstract_exact_selector_test over to dart2js since it's a
dart2js-specific regression test and not an actual language test.
- Migrate corelib/apply_test.dart.
- Delete abstract_beats_arguments[2]_test.dart since that code is
statically wrong in 2.0 and can't be run.
This doesn't get the dart2js bots running the new suites. I'll email
the relevant folks to get help with that.
* Resurrect abstract_beats_arguments_test.dart.
It usefully checked that an implementation reports an warning (now
error) if you construct an abstract class.
Also added support to test.dart to mark a test as expecting to
generate a compile error in the test itself. That way, the status file
reflects what is *wrong* about the current status, not what is *right*.
* Change static error syntax to match front_end notation.
* Migrate abstract_getter_test.
Ben Konyi