Add Wasm testing in Chromium, not just command-line `v8` (#40786)
This should give us a better idea of any cases where browser and JS engine behaviour diverge. * Uses WebSockets to write pipe console messages to the test runner. * Skip System.Net.Http FunctionalTests depending on X509 certificates, tests discovery fails on `System.Net.Http.Functional.Tests.HttpClientEKUTest..cctor()` which ends up throwing PNSE * Added environment variable to help platform detect when we're running in the browser vs v8 * System.Net.Http LoopbackServer: fix NullReferenceException because we were trying to dispose a Socket instance that threw PNSE in the constructor Co-authored-by: NAnkit Jain <radical@gmail.com> Co-authored-by: NSteve Pfister <steve.pfister@microsoft.com> Co-authored-by: NLarry Ewing <lewing@microsoft.com> Co-authored-by: NAlexander Köplinger <alex.koeplinger@outlook.com>
Showing
想要评论请 注册 或 登录