-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Compile Microsoft.Extensions.HostFactoryResolver test file #52194
Conversation
Tagging subscribers to this area: @eerhardt, @maryamariyan |
@eerhardt this seems to have broken a lot of the runtime-staging tests. |
@lewing - which ones? All the runtime checks passed on this PR. |
runtime-staging doesn't fail in a clear way https://dev.azure.com/dnceng/public/_build/results?buildId=1118930&view=results |
The first one I looked into has:
which looks like it should be #34582. All of the "host" tests are marked with this active issue:
|
The Android and TvOS runs of that build appear to be unrelated/not the new tests failing. The 2 browser-wasm legs appear to be failing for a different reason than Windows above:
Is there an easy way to debug into this configuration? |
It is definitely more than this PR, I think my information may have been wrong. |
Given the two new browser lanes that failed (EAT, AOT) I suspect they are aggressive trimming related. |
Fix #52118