[infra] Shard dart2js modular tests * Shard dart2js modular tests (and decrease the shards of the unit tests) * Remove folders we look for dart files in --- the remove folders doesn't contain any anyway and would have to be copied if keeping these lines. * Fix sharding, previously trying to shard in 2 shards would only allow you to run ~50% of the tests: ``` $ out/ReleaseX64/dart-sdk/bin/dart pkg/compiler/tool/modular_test_suite.dart -nweb-unittest-asserts-linux --verbose --use-sdk --shards=2 --shard=0 Error: shard should be between 0 and 1, but got 0 $ out/ReleaseX64/dart-sdk/bin/dart pkg/compiler/tool/modular_test_suite.dart -nweb-unittest-asserts-linux --verbose --use-sdk --shards=2 --shard=2 Error: shard should be between 0 and 1, but got 2 ``` This has been corrected to allow from `1..n` for `n` shards to fit with what the testing system sends when specifying `shards` in `tools/bots/test_matrix.json`. For previous try runs I extracted this: Build 60615: Shard #1: --- Total time: 04:27 --- Shard #2: --- Total time: 05:19 --- Shard #3: --- Total time: 04:23 --- Shard #4: --- Total time: 10:29 --- => A total of 24:35 --- combined finish of 10:29 Modular tests: 32:19 Total bot runtime: 35:48 Build 60614: Shard #1: --- Total time: 03:57 --- Shard #2: --- Total time: 05:18 --- Shard #3: --- Total time: 05:21 --- Shard #4: --- Total time: 05:34 --- => A total of 20:10 --- combined finish of 5:34 Modular tests: 29:41 secs Total bot runtime: 35:55 Build: 60613 Shard #1: --- Total time: 03:56 --- Shard #2: --- Total time: 05:15 --- Shard #3: --- Total time: 04:32 --- Shard #4: --- Total time: 05:34 --- => A total of 19:17 --- combined finish of 5:34 Modular tests: 33:39 Total bot runtime: 38:51 With the new sharding I'd estimate that the unit tests and modular tests would have finished in less than 13 minutes, making the bots finish in ~17 minutes, ~20 minutes and ~19 minutes instead. The try-run with this ran in 17:06 Possibly a follow-up could do more stuff on the "main bot". Change-Id: Ie5c96206deb9c0c6db3385bbca04ae6f4eab4c3a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/448381 Reviewed-by: Nate Biggs <natebiggs@google.com> Reviewed-by: Ivan Inozemtsev <iinozemtsev@google.com> Commit-Queue: Jens Johansen <jensj@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.