commit | 8e70c040127edf0b17eca61648da2836d36c3e19 | [log] [tgz] |
---|---|---|
author | Martin Kustermann <kustermann@google.com> | Sat Jul 17 13:21:14 2021 +0000 |
committer | Martin Kustermann <kustermann@google.com> | Sat Jul 17 13:21:14 2021 +0000 |
tree | 2b60a210618a07518305069915d6fdbf1b25d7f7 | |
parent | 5c0466a14f61d08d90761eee900dc6386d3cdc12 [diff] |
[vm/concurrency] Remove unix_socket_test.dart from iso-stress builder The test causes flaky issues when run in parallel, it may also have client/server races in them. The flaky failures happen due to a socket write resulting in a "broken pipe" exception. Normally that means the other end of the socket was closed whent the write happens. An attempt in [0] at fixing one of the issues seem to be unsuccessful, since the error still happens, namely in this code: final serverContinue = Completer(); final clientContinue = Completer(); server.listen((s) async { await serverContinue.future; clientContinue.complete(); }); final socket = await Socket.connect(address, server.port); socket.write(" socket content"); // <-- This write causes a broken pipe exception! serverContinue.complete(); await clientContinue.future; It's unclear why that happens, since the server side certainly doesn't close it's end of the socket. Since this is causing "iso-stress" builder to be failing, I'll remove this test from the stress test. Issue https://github.com/dart-lang/sdk/issues/36097 TEST=Removing test from "iso-stress" builder Change-Id: I1f9fc130b7408d586b55699487baa3c293403217 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/207134 Reviewed-by: Martin Kustermann <kustermann@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.