[browser][MT] System.Xml.Tests.TC_SchemaSet_Add_URL.v4

[simonrozsival]

The test internally calls the XmlDownloadManager which makes a GET HTTP request to http://bla/ and at that point the test execution gets stuck and eventually timeouts. I assume that this is caused by making a HTTP request on a non-browser thread but there might be something else going on.

Ref #74408

Stack:

-> using (Stream respStream = await client.GetStreamAsync(uri).ConfigureAwait(false))
-> return GetNonFileStreamAsync(uri, credentials, proxy).GetAwaiter().GetResult();
-> XmlDownloadManager.GetStream(absoluteUri, _credentials, _proxy);
-> stream = (Stream?)_laterInitParam.inputUriResolver.GetEntity(_laterInitParam.inputbaseUri, string.Empty, typeof(Stream));
-> FinishInitUriString();
-> XmlResolver tmpResolver = GetXmlResolver() ?? GetDefaultPermissiveResolver();
-> XmlReader reader = XmlReader.Create(schemaUri, _readerSettings);
-> sc.Add("xsdauthor", "http://Bla");

GetNonFileStreamAsync is called with a comment:

// This code should be changed if HttpClient ever gets real synchronous methods.  For now,
// we just use the asynchronous methods and block waiting for them to complete.

Expected exception form the hanging function: [out of order message from the browser]: http://bla/ - Failed to load resource: net::ERR_NAME_NOT_RESOLVED

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The test internally calls the XmlDownloadManager which makes a GET HTTP request to http://bla/ and at that point the test execution gets stuck and eventually timeouts. I assume that this is caused by making a HTTP request on a non-browser thread but there might be something else going on.

Author:	simonrozsival
Assignees:	-
Labels:	arch-wasm, area-Build-mono
Milestone:	8.0.0

[lewing]

@pavelsavara @lambdageek @kg this would be a good first issue for threaded js interop

[kg]

I wonder if unhandled exceptions in workers get forwarded to the console during tests?

[pavelsavara]

I wonder if unhanded exceptions in workers get forwarded to the console during tests?

We improved it here #74751