-
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
Update Mac Builders #26057
Comments
related #26057 Review URL: https://codereview.chromium.org/1821203002 .
@zanderso is there something still to be done here? Closing this as stale, but please reopen if something still needs to happen. |
The test is actually failing on Mac. |
We have a PR on gRPC (grpc/grpc-dart#472) which can't land because client certificates handling is (seemingly?) broken on Mac. Unfortunately I can't figure out what exactly is wrong because Handshake exception one gets is extremely uninformative. /cc @aam |
@mraleph were you able to reproduce the failure locally? |
Here is what I get on my mac (10.15.7) $ dart tests/standalone/io/secure_server_client_certificate_test.dart
unittest-suite-wait-for-done
Unhandled exception:
HandshakeException: Connection terminated during handshake the same test passes on Linux. |
Unfortunately it passes on my mac 11.3.1 at https://dart.googlesource.com/sdk/+/9a9e854515278b90437ea27063af64e5c3df05aa. It also seems to pass on buildbots. |
Bummer. I guess we will have to wait and see what happens when we update the bots to 10.14 (or get those Apple Silicon bots which are running 11). If I have some time I will try to instrument the VM to print more informative handshake message. Lets close this for now then. |
Fixes #26057 Change-Id: I172f7b8221f34d2bd16df324d96ad7a6ec88d54d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/199301 Commit-Queue: Vyacheslav Egorov <vegorov@google.com> Reviewed-by: Vyacheslav Egorov <vegorov@google.com>
And reenable the test standalone/io/secure_server_client_certificate_test after.
/cc @iposva-google @whesse
The text was updated successfully, but these errors were encountered: