-
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
dart analyze
crashes after reporting "No issues found!"
.
#48584
Comments
The situation fixed in https://dart-review.googlesource.com/c/sdk/+/234660 is that a crash occurs, and then the process hangs. I fixed it so that the crash still occurs, and the process exits. Are you saying that change introduced a second crash? |
As the analysis_server crashes, this is a bug either with the Dart VM, or with fsatrace. @rmacnak-google asserts it is a bug with fsatrace. |
I think so, since the dart analyzer consistently fails our builds now. Except this second crash happens specifically happens after the dart analyzer logs |
Ah I see. Thanks for clarifying. How can I reproduce this? |
In the past this has been flakey in infra and locally, but since this is reproducing more often in infra I'll see if I can try to get a clear local repro case. |
Do we get any sort of a stack trace from the crashing of fsatrace + dart? |
@srawlins -- What is the status with this issue? LMK if I can be of any help. |
There's no stack trace available, but I suspect the issue is that the analysis server shutdown timeout is too short. I'm testing this theory out and will upload a CL if that ends up being the case. |
Just sent out https://dart-review.googlesource.com/c/sdk/+/237780 which should fix the issue. Thanks @chaselatta for helping me figure this out! |
It seems that https://dart-review.googlesource.com/c/sdk/+/234660 has inadvertently caused crashes even when the analylzer says "No issues found!".
See #48413 for additional context.
See https://logs.chromium.org/logs/turquoise/buildbucket/cr-buildbucket/8819654207538277009/+/u/build/failure_summary and https://chat.google.com/room/AAAABFiUm4o/iCzaNBjqgdY for the crash.
CC: @srawlins, @rmacnak-google
The text was updated successfully, but these errors were encountered: