| commit | cc5f351c3499bf06b0468f481e2a76d3a236f28e | [log] [tgz] |
|---|---|---|
| author | Liam Appelbe <liama@google.com> | Mon Jul 07 16:15:51 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 07 16:15:51 2025 -0700 |
| tree | 6911b9274f9c3fb23a36a451621c5535001303f2 | |
| parent | 2242b2b61c137c1f5fbfeece8387c91319122c1b [diff] |
Revert "[test_runner] Improve timeout deflaking" This reverts commit f95a84da5c9817a001139094ef63adac4bf5ad52. Reason for revert: Testing if CL caused increased meta-flakiness of non-timeout failures. Bug: https://github.com/dart-lang/sdk/issues/55044 Original change's description: > [test_runner] Improve timeout deflaking > > The usual deflaking logic is to simply rerun the test 5 times, but if the failure was a timeout this can be very expensive. Instead, only rerun timeout failures twice, and use the last successful run time to set a tighter timeout. > > Repeat counts and timeouts are now per-test. The name, repeat count, and timeout make a `DeflakeInfo`. This object is constructed in compare_results.dart, and passed to test.py's `--tests` flag. The recipe was already passing the output of compare_results directly to that flag, so no change is needed to the recipies. > > Backwards compatibility: > > If you want the old behavior of compare_results.dart, use the `--name-only` flag. > > test.py only uses this new logic if it detects that the `--tests` flag is JSON (if it starts with a `{`). > > Change-Id: I4113b68c54bfb7fd9a5e8fc9dab7a265807f3e77 > Bug: https://github.com/dart-lang/sdk/issues/55044 > Fixes: https://github.com/dart-lang/sdk/issues/55044 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/435760 > Commit-Queue: Liam Appelbe <liama@google.com> > Reviewed-by: Alexander Thomas <athom@google.com> Bug: https://github.com/dart-lang/sdk/issues/55044 Change-Id: I68268dcaffbe857ccec20e211c34325c03643b37 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/439180 Commit-Queue: Liam Appelbe <liama@google.com> Reviewed-by: Siva Annamalai <asiva@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.