commit | 30ae8e3d1438a01158c9033f21be0c75dbacca34 | [log] [tgz] |
---|---|---|
author | Jens Johansen <jensj@google.com> | Thu Jan 28 07:46:10 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 28 07:46:10 2021 +0000 |
tree | 334750f4b2e6b23f1b9aaece14f98278f40234f0 | |
parent | 7bbab07bea37a423fc143bae646ad22ce156febe [diff] |
[CFE] Rename tests that require git; split unit_test_suites; filter tests better This CL is a warm-up to a follow-up change that will make running the CFE trybot faster. This CL: * Rename tests that require git (because when working with filesets and shards in the test system, the "checkout" is not a git checkout and git commands thus doesn't work properly. * Filters the front-end unit test setup on the front-end bot the way it was probably intended, i.e. run tests in pkg/kernel, pkg/front_end and pkg/fasta (actually, the last one doesn't exist, but still) instead of just in folders inside the "suite" 'pkg' that somewhere in the path has something called 'kernel', 'front_end' or 'fasta'. * Split unit_test_suites.dart into a "forwarding shell" and a impl. In a follow-up CL the impl will be converted to nnbd to allow for using 'required' on named parameters, but if the entry point was nnbd it would run in sound nnbd mode and nothing would compile because all imports are not nnbd. Overall this CL should change very little, mostly just run a few less tests, i.e. for instance skip tests that live inside a folder called 'fasta' somewhere inside the analyzer directory path. Change-Id: I3226c7261cff8b68cc287cff07dc1715dfd85159 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/181381 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.