Skip to content

Update branding to 9.0.303#49654

Merged
nagilson merged 2 commits intodotnet:release/9.0.3xxfrom
vseanreesermsft:branding-9.0.303-2025-07-03-1036-be96cd46-da6b-4c23-ac52-3fae39d37f76
Jul 8, 2025
Merged

Update branding to 9.0.303#49654
nagilson merged 2 commits intodotnet:release/9.0.3xxfrom
vseanreesermsft:branding-9.0.303-2025-07-03-1036-be96cd46-da6b-4c23-ac52-3fae39d37f76

Conversation

@vseanreesermsft
Copy link
Copy Markdown
Contributor

No description provided.

@SimonZhao888
Copy link
Copy Markdown
Member

New test failure, error message:

Failed Microsoft.NET.Restore.Tests.GivenThatWeWantToUseFrameworkRoslyn.It_downloads_Microsoft_Net_Compilers_Toolset_Framework_when_requested [26 s]
  Error Message:
   The command output did not contain expected result: C:\h\w\B14E098C\t\dotnetSdkTests\3ypf0ew2.hmz\It_downloads_---E90CE74D\nuget-packages\microsoft.net.sdk.compilers.toolset\9.0.303-ci\csc.exe /noconfig

File Name: C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\msbuild.exe
Arguments: /t:Build C:\h\w\B14E098C\t\dotnetSdkTests\3ypf0ew2.hmz\It_downloads_---E90CE74D\NetCoreApp\NetCoreApp.csproj /restore
Exit Code: 0
StdOut:
MSBuild version 17.14.10+8b8e13593 for .NET Framework

@nagilson
Copy link
Copy Markdown
Member

nagilson commented Jul 7, 2025

Oh goodness. That looks like the #42822 failure from a year ago. It would be ideal to update the test to contain the expected vs actual output bc I have no idea what it did without running it myself and debugging into it.

That test had issues in the past, I wonder if it has to be updated again. @jjonescz thanks for fixing this test in the past. Are you familiar with this logic, do you think it needs to be updated again?

@nagilson
Copy link
Copy Markdown
Member

nagilson commented Jul 7, 2025

I might just skip it again for now to unblock this as this is blocking a bunch of other stuff.

@nagilson
Copy link
Copy Markdown
Member

nagilson commented Jul 7, 2025

I wonder if this is related to the JIT / Compiler issue, though thats 10.0 preview 6, so probably not.

This test failed a year ago almost from today and is blocking everything from flowing in.
Let's use the existing closed issue to start tracking the test problem again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants