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

[MSBuild Server] Manual exploratory testing and measurement #6427

Closed
rokonec opened this issue May 7, 2021 · 1 comment
Closed

[MSBuild Server] Manual exploratory testing and measurement #6427

rokonec opened this issue May 7, 2021 · 1 comment
Assignees
Labels
performance Performance-Scenario-Build This issue affects build performance. triaged
Milestone

Comments

@rokonec
Copy link
Member

rokonec commented May 7, 2021

Test, verify and measure

Work breakdown:

  • Test on Windows .NET, Windows .NET 5, Linux .NET 5 5, OSx .NET 5
  • Test architectures 32, 64
  • Test corner cases
    • Concurrent builds
    • Build cancellation
    • Failed builds
    • MSBuild server process killing
    • Build after Server TTL
  • Test and measure simple projects
  • Test and measure complex projects
  • Measure inner-loop cold scenarios
  • Measure inner-loop hot scenarios
@rokonec rokonec added the needs-triage Have yet to determine what bucket this goes in. label May 7, 2021
@rokonec rokonec changed the title [MSBuild Server] manual exploratory testing [MSBuild Server] manual exploratory testing and measurement May 7, 2021
@rokonec rokonec changed the title [MSBuild Server] manual exploratory testing and measurement [MSBuild Server] Manual exploratory testing and measurement May 7, 2021
@rokonec rokonec mentioned this issue May 7, 2021
7 tasks
@rokonec rokonec added performance Performance-Scenario-Build This issue affects build performance. and removed needs-triage Have yet to determine what bucket this goes in. labels May 7, 2021
@rokonec rokonec self-assigned this May 7, 2021
@rokonec
Copy link
Member Author

rokonec commented Jun 21, 2021

Some measurement has been done in: Create fully functional prototype and measure it #6467

Feature has been parked into: https://github.com/dotnet/msbuild/tree/feature/msbuild-server-v2--parked

@rokonec rokonec closed this as completed Jun 21, 2021
@ladipro ladipro added this to the VS 17.0 milestone Dec 8, 2021
JaynieBai pushed a commit that referenced this issue Feb 8, 2023
)

Bumps Microsoft.CodeAnalysis.BannedApiAnalyzers from 3.3.3 to 3.3.4.

Release notes
Sourced from Microsoft.CodeAnalysis.BannedApiAnalyzers's releases.

v3.3.4
Release build of Roslyn-analyzers based on Microsoft.CodeAnalysis 3.3.1 NuGet packages. Works with VS 2019 16.9 or later.

Contains important functionality and performance bug fixes on top of v3.3.3 release
Commits
22ea642 Merge pull request #6436 from ViktorHofer/patch-1
9018071 Fix buildtransitive vs buildTransitive difference
afa5665 [main] Update dependencies from dotnet/arcade (#6423)
afee469 Merge pull request #6427 from mavasani/CodeAnalysisTreatWarningsAsErrors_Glob...
b858999 Merge pull request #6430 from dotnet/locfiles/be3abf9f-1f22-469b-b26d-7648587...
0cbc3c5 Localized file check-in by OneLocBuild Task: Build definition ID 830: Build I...
113dadc Merge pull request #6429 from dotnet/revert-6364-net7-tests
356147f Revert "Move tests to target .NET 7"
1d7244a Update documentation for CodeAnalysisTreatWarningsAsErrors implementation
6c028d3 Re-implement CodeAnalysisTreatWarningsAsErrors with globalconfig files
Additional commits viewable in compare view
@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Performance-Scenario-Build This issue affects build performance. triaged
Projects
None yet
Development

No branches or pull requests

3 participants