-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dart2Wasm async/async*/yield/yield* umbrella issue #55025
Comments
Current list of tests that are hanging:
https://dart-review.googlesource.com/c/sdk/+/354621 starts to skip these tests. |
Please list all tests skipped by this issue, so it can be found when searching. |
I started looking into why these fail. It takes time to find the root cause, but most of them involve error handling or cancellation (which I suspect may be relying on error handling). So I think it makes sense to start fixing with #52464. |
Those timing out tests cause CI infra issues (purple bots) on deflaking. Issue #55025 Change-Id: Ibdc3766e0e482f180c03acc987c3323a3574647c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/354621 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: William Hesse <whesse@google.com> Auto-Submit: Martin Kustermann <kustermann@google.com>
After fixing test infra structure to recognize async tests, putting in a workaround for Chrome/V8 bug not reporting
are failing on configurations
|
I'm currently running into this issue:
Example code: Stream<String> call() async* {
yield* combinedFolded; // errors here
} Should this now be fixed, or should I open a new issue? Version:
|
@IchordeDionysos – please open a seperate issue! |
There's a number of semantics issues with Dart2Wasm's implementation for async/async*/yield/yield* implementation (mostly async* related I believe). We use this tracking number in approvals & status files.
yield*
desugaring doesn't handle errors correctly #52464/cc @osa1
The text was updated successfully, but these errors were encountered: