-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update Roslyn to 4.13.0-1.24510.9 #109467
Conversation
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
@@ -380,17 +380,17 @@ | |||
<Uri>https://github.com/dotnet/runtime-assets</Uri> | |||
<Sha>8254bfd574d0f7a89450a2e191d9e9f3dfb8ad59</Sha> | |||
</Dependency> | |||
<Dependency Name="Microsoft.Net.Compilers.Toolset" Version="4.12.0-3.24523.10"> | |||
<Dependency Name="Microsoft.Net.Compilers.Toolset" Version="4.13.0-2.24531.4"> |
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.
dfa1ca0
to
107202c
Compare
/ba-g hanging browser tests and unrelated browser test failures |
It appears that this PR introduced hangs/timeouts in CLR_Tools_Tests. CLR_Tools_Tests is failing with hang/timeout in all PRs. I am validating whether the CLR_Tools_Tests hang/timeout goes away in #109495. |
https://dev.azure.com/dnceng-public/public/_build/results?buildId=858785&view=results is the first one I see that has the timeout. The diff with the previous build is 598d5f7...275ea58 - I think #109392 is the culprit. Reverting in #109520. |
Based on #108789.
Resolve VMR failures seen in dotnet/sdk#43015