async_await_test was correct, but was using a misleading name. It really
cares about assertions being enabled, not "checked mode".
The setter tests originally validated the runtime type checks but were
changed to compile time checks. Used a little judicious dynamic to get
back to testing the runtime type checking.
Change-Id: I0e121bd1443376e885777d609f5d6507537c0b8c
Reviewed-on: https://dart-review.googlesource.com/14161
Commit-Queue: Bob Nystrom <rnystrom@google.com>
Reviewed-by: Janice Collins <jcollins@google.com>
This adds analyzer-strong-checked as distinct from analyzer-strong,
which seems to be how the bots run it. Also adds the d8 runtime to dart2js as that was the cause of some bot breakage.
Finally, you can now run one test by just passing a single parameter.
BUG=
R=bkonyi@google.com, jmesserly@google.com
Review-Url: https://codereview.chromium.org/2997673002 .
This looks at all the files in the batch being migrated. It goes through
the status files in the 1.0 and strong directories. If it sees an entry
that matches that file, it adds it to the resulting "_2" status file.
It handles adding entries to an existing section if already present in
the new status file. Otherwise, it adds a new section at the end with
the entries.
R=bkonyi@google.com
Review-Url: https://codereview.chromium.org/2989033002 .
- Track files that only exist in the "_2" directories. That way we can
show what work still remains to be done even if the unmigrated files
are gone.
- Friendlier matching of command line arguments. Pass in any substring
of the test path and if only one test matches, it will be used.
- Make --dry-run not crash.
R=bkonyi@google.com
Review-Url: https://codereview.chromium.org/2988973002 .
Paul Berry