-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
PhysicalFileProvider: Avoid NullRef if ResolveLinkTarget returns null #57235
Conversation
Tagging subscribers to this area: @maryamariyan, @dotnet/area-extensions-filesystem Issue DetailsSpotted the following exception in #57229 (helix log)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering whether this is unit testable. (Although clearly other tests will ?sporadically hit it)
@danmoseley in theory the steps to test this is have a callback in the |
Lots and lots of staging failures. I went through most failure in Mono Windows Microsoft.Extensions.Hosting.Tests.ConsoleLifetimeExitTests.EnsureEnvironmentExitDoesntHang already tracked by #57184 The test libraries on Catalyst reports show up as "The Helix Work Item failed. Often this is due to a test crash or infrastructure failure. See the Helix Test Logs tab in the Results page of Azure DevOps." but when I look at artefacts, there's a testResults.Xml present with results in it -- @steveisok ? I think that's more interesting to fix than the actual failures.
Android has the same issue with not extracting results from the test results XML these two failures both seem related to appcompat switches?
Turkish I
various others No evidence that any of these are caused by this PR. We may be in a bind here where something has broken these specifically because they don't block checkin? |
@danmoseley #57114 should address these. There was a prior commit that stopped runtimeconfig.json from being processed. On mobile, we generate a bin file from runtimeconfig.json |
@steveisok thanks, following back to what caused that it seems it was #56486 but it looks like staging passed 100% before that was committed? |
The only non staging failure was the async one fixed in a parallel PR. |
Spotted the following exception in #57229 (helix log)