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
Remove some outdated configurations in tools #52800
Conversation
Any comment on this PR? Are these changes wanted? |
src/Features/Lsif/Generator/Microsoft.CodeAnalysis.LanguageServerIndexFormat.Generator.csproj
Show resolved
Hide resolved
@@ -2,17 +2,10 @@ | |||
<!-- Licensed to the .NET Foundation under one or more agreements. The .NET Foundation licenses this file to you under the MIT license. See the LICENSE file in the project root for more information. --> | |||
<Project Sdk="Microsoft.NET.Sdk"> | |||
<PropertyGroup> | |||
<Platform Condition="'$(Platform)' == ''">x64</Platform> | |||
<PlatformTarget>x64</PlatformTarget> | |||
<Platforms>x64</Platforms> |
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.
🤷♂️ This change doesn't seem necessary but will leave for @dotnet/roslyn-compiler to review
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.
Still needs two sign-offs from compiler
@huoyaoyuan could you bring this PR up to date? Moving to draft in the meantime. Thanks! |
@CyrusNajmabadi Done |
Apologies. The team is small at the moment and we've not reviewed this PR in a timely fashion. As a result it went out-of-date with other changes that went in... |
@jcouv Updated. Most of the conflicts are about updating
I will be interested if you consider to hire more members in the future 😄 |
{909B656F-6095-4AC2-A5AB-C3F032315C45}.Debug|Any CPU.ActiveCfg = Debug|Any CPU | ||
{909B656F-6095-4AC2-A5AB-C3F032315C45}.Debug|Any CPU.Build.0 = Debug|Any CPU | ||
{909B656F-6095-4AC2-A5AB-C3F032315C45}.Release|Any CPU.ActiveCfg = Release|Any CPU | ||
{909B656F-6095-4AC2-A5AB-C3F032315C45}.Release|Any CPU.Build.0 = Release|Any CPU |
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.
nit: I noticed that some x64
configurations are left in this file. Should they be switched too?
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 Thanks (iteration 9)
@dotnet/roslyn-compiler for second review. Thanks |
@dotnet/roslyn-compiler for another review. Thanks |
2 similar comments
@dotnet/roslyn-compiler for another review. Thanks |
@dotnet/roslyn-compiler for another review. Thanks |
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
Thanks for the contribution @huoyaoyuan ! |
Lesson learned from this change: The removal of Putting out a PR to fix that but something we should keep in mind for future changes like this. |
This fixes the following issues in Rebuild validation 1. Adds back `<PlatformTarget>AnyCPU</PlatformTarget>` so the exe runs under x64 in CI. Running in x86 in CI is putting us right up against the memory boundary and sometimes results in crashes. 2. Changes `LocalReferenceResolver` such that directories are only enumerated twice (once for exe and one for dll). In the past every new name request caused the entire directory set to be walked again. This change saved ~8 seconds on our CI runs. 3. When there is a misc error record it in the build artifacts instead of silently failing. Related: dotnet#52800
Is |
* Rebuild fixes This fixes the following issues in Rebuild validation 1. Adds back `<PlatformTarget>AnyCPU</PlatformTarget>` so the exe runs under x64 in CI. Running in x86 in CI is putting us right up against the memory boundary and sometimes results in crashes. 2. Changes `LocalReferenceResolver` such that directories are only enumerated twice (once for exe and one for dll). In the past every new name request caused the entire directory set to be walked again. This change saved ~8 seconds on our CI runs. 3. When there is a misc error record it in the build artifacts instead of silently failing. Related: #52800 * PR feedback
Introduced in 2016. I can't imagine any reason to run on x64 only today.
Defaults to on now.
The only remaining non-AnyCPU project is BuildActionTelemetryTable, which depends on x86 implementation of GetHashCode. With VS2022 moving to x64, it can be also moved to AnyCPU in dev17.