| commit | f827eb3a78e3b3ff8352ece9f35ed94b52e1d917 | [log] [tgz] |
|---|---|---|
| author | Jonas Termansen <sortie@google.com> | Wed Jul 19 12:24:38 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 19 12:24:38 2023 +0000 |
| tree | b19e0c41ed8d6c6faf626c7382c82c60d0d2e8bc | |
| parent | a746b64aa78f61341d8821dc87e99e0b670cb28e [diff] |
Balance tests equally across shards. The sharded test runner invocations are now passed the previous results which contains the test timing, which are used to simulate how long each shard would take to run. The shards are now balanced as evenly as possible on a test level, taking multiple cores into account. Sharded tests are now run starting with the slowest test first, such that extremely long running tests finish as early as possible. This behavior ensures the cores are saturated and can be padded with fast tests near the end, rather than waiting for a few slow tests to complete while the rest of the system is idle. The algorithm works very well whenever it's able to accurately predict the time to run shards. In a number of cases, the model doesn't quite reflect reality and the data, which makes it fairly imperfect but still reasonably good. I think a second order feedback loop might kick in once it reorders the tests across shards and the test timing data reflects the new test timings. Multitests are no longer always sent to the same shard, since the data isn't available at the moment, and the change as-is speeds up the test running considerably. The front end unit test suites currently ignore the feature as there are no benefits yet to improving those quick shards. Upgrade the language version to 3.0.0 so patterns can be used and fix a mixin not being a mixin. Fixes: b/291585137 Change-Id: I3cc1b1d96038d5b46e836b091e299097717c226c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/314081 Reviewed-by: William Hesse <whesse@google.com> Commit-Queue: Jonas Termansen <sortie@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.