Skip to content
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

[main] Update dependencies from dotnet/roslyn #82479

Merged
merged 11 commits into from
Mar 3, 2023

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Feb 22, 2023

This pull request updates the following dependencies

From https://github.com/dotnet/roslyn

  • Subscription: 0af788c4-77ba-425c-b8c9-08da91234a73
  • Build: 20230303.1
  • Date Produced: March 3, 2023 10:47:55 AM UTC
  • Commit: 83631c4ff921167567b7a5ba6ea5e7e5bf1e6661
  • Branch: refs/heads/main

…221.6

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-2.23120.1 -> To Version 4.6.0-2.23121.6
@lewing
Copy link
Member

lewing commented Feb 22, 2023

Don't merge until we have a plan for #82466

@lewing lewing added the area-codeflow for labeling automated codeflow label Feb 22, 2023
@hoyosjs hoyosjs added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 22, 2023
…222.3

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23122.3
…223.15

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23123.15
@lewing
Copy link
Member

lewing commented Feb 25, 2023

The parameter fix should flow here soon and we should undo the the workaround to verify before merging

dotnet-maestro bot and others added 7 commits February 25, 2023 13:34
…225.1

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23125.1
…226.1

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23126.1
…226.2

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23126.2
…228.2

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23128.2
…301.1

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-2.23151.1
…302.1

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-3.23152.1
@lewing lewing removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 2, 2023
@lewing
Copy link
Member

lewing commented Mar 2, 2023

@jaredpar any idea what might cause all the new CS8601 here?

@jaredpar
Copy link
Member

jaredpar commented Mar 2, 2023

@lewing yes, sent a PR to proactively fix these up a few days ago but lost track of it in some infra fires. Let me go clean that one up real quick.

#82803

…303.1

Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
 From Version 4.6.0-1.23073.4 -> To Version 4.6.0-3.23153.1
@lewing lewing closed this Mar 3, 2023
@lewing lewing reopened this Mar 3, 2023
@lewing
Copy link
Member

lewing commented Mar 3, 2023

Wbt failure is #80619

     In value:  [l1ibpu0v.fcd-stderr] System.IO.IOException: The system cannot open the device or file specified. : 'NuGet-Migrations'
                 [l1ibpu0v.fcd-stderr]    at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
                 [l1ibpu0v.fcd-stderr]    at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
                 [l1ibpu0v.fcd-stderr]    at NuGet.Common.Migrations.MigrationRunner.Run()
                 [l1ibpu0v.fcd-stderr]    at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
                 [l1ibpu0v.fcd-stderr]    at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, IAspNetCertificateSentinel aspNetCertificateSentinel, IFileSentinel toolPathSentinel, Boolean isDotnetBeingInvokedFromNativeInstaller, DotnetFirstRunConfiguration dotnetFirstRunConfiguration, IEnvironmentProvider environmentProvider, Dictionary`2 performanceMeasurements)
                 [l1ibpu0v.fcd-stderr]    at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
                 [l1ibpu0v.fcd-stderr]    at Microsoft.DotNet.Cli.Program.Main(String[] args)
                 [l1ibpu0v.fcd-stderr] 

@lewing
Copy link
Member

lewing commented Mar 3, 2023

coreclr failure looks like #82771

@lewing lewing merged commit 13d1801 into main Mar 3, 2023
@dotnet-maestro dotnet-maestro bot deleted the darc-main-47d6bab6-a022-4c94-b153-bbe74de2c0f1 branch March 3, 2023 19:21
radical added a commit to radical/runtime that referenced this pull request Mar 3, 2023
`/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignment`

Started being hit with dotnet#82479 .
The other instances of this were fixed in
dotnet#82803 .
radical added a commit that referenced this pull request Mar 3, 2023
* [wasm] Debugger tests - fix build

`/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignment`

Started being hit with #82479 .
The other instances of this were fixed in
#82803 .

* CI: Trigger all the wasm jobs, when roslyn is updated

And this includes the debugger tests
@ghost ghost locked as resolved and limited conversation to collaborators Apr 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-codeflow for labeling automated codeflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants