pkg/dds/test/dap/integration/debug_exceptions_test went from flaky -> RuntimeError on unittest-asserts-release-win-arm64 about sdk HOT 4 OPEN

I guess many of those failures could be the drive letter issue. Let's land the fix above and then review the stats.. if there are still failures and that wasn't a one-off, I'll open a change to add verbose output and we can go from there.

(I'll ping back here a little after that fix lands)

from sdk.

cc @bkonyi and @DanTup

from sdk.

https://dart-review.googlesource.com/c/sdk/+/365804 should fix the drive letter mismatch (oddly that test hasn't changed in 2yrs.. not sure if the drive letter casing is somehow different on some bots for temp directory?).

Hard to tell what the other failure is - @derekxu16 is there a way to tell how frequently it's failing? We could enable verbose output on the bots temporarily to try to get a better idea of what's happening?

from sdk.

We have a flakiness dashboard. Unfortunately you have to log in with an @google.com account to access it, but here's a screenshot showing the run results of pkg/dds/test/dap/integration/debug_exceptions_test on Windows:

I don't know how many of these failures were caused by SocketExceptions specifically, but the test is failing frequently.

from sdk.