-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
pkg/dds/test/dap/integration/debug_attach_test fails on pkg-win-release-arm64 #55705
Comments
I'm seeing a slightly different error when I run locally (intermittently):
It's possible they're the same issue and there's just a timing difference causing it to show up differently. I'll debug/fix this and we can check the bot results after. |
@bkonyi I can only reproduce the error above when running from the terminal - any time I run with a debugger it does not occur. My feeling is that when debugging, the timing is slightly different. Unfortunately from the terminal, the stack trace is not very useful - there is no user code in it:
Can you think of any ways I might be able to track down where this is happening? From the stack trace, I thought maybe I was using I don't know if something like the "asyncCausalFrames" we use via the VM Service would help here, but without reproducing with a debugger attached I'm not sure if I could get them to see. Edit: I tried running with |
This might be different race. This one is due to how during test session tearDown, client queues command "terminate" to the server's stdin, which races with server process itself shutting down first closing stdin socket, before that "terminate" command has a chance of being written into that server's stdin. |
Move discussion of this to #55313 (comment) As for the original issue here: The Edit: Opened https://dart-review.googlesource.com/c/sdk/+/366640 to improve the failure message. |
This improves the failure messages that will show in tests if a DAP request unexpectedly fails. Before: ``` Instance of 'Response' ``` After: ``` Request "evaluate" failed: { "seq": 17, "type": "response", "body": { "error": { "format": "{message}", "id": 1, "showUser": true, "variables": { "message": "This is a test failure", "stack": "#0 DartDebugAdapter.evaluateRequest (package:dds/src/dap/adapters/dart.dart:1046:5)\n#1 (SNIP)\n" } } }, "command": "evaluate", "message": "This is a test failure", "request_seq": 8, "success": false } ``` Might help diagnose #55705. Change-Id: If9edad16090a8bd09e22dd9b772401763d281f8b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/366640 Commit-Queue: Helin Shiah <[email protected]> Reviewed-by: Ben Konyi <[email protected]> Reviewed-by: Helin Shiah <[email protected]>
Here's an example failure from one of the logs after this change:
|
@sstrickl that's actually a different issue that was caused by my change :-( Unfortunately I don't think the right trybots ran on https://dart-review.googlesource.com/c/sdk/+/366640 so it wasn't stopped. I've opened a fix for that at https://dart-review.googlesource.com/c/sdk/+/366665 That issue shouldn't affect this test though - if debug_attach_test fails we should get a more detailed error like that, although I'm struggling to find if it is currently failing (I tried https://dart-ci.firebaseapp.com/#showLatestFailures=false&configurations=pkg-win-release-arm64 and don't see it, but I don't know if approved failures appear there?). |
from logs
The text was updated successfully, but these errors were encountered: