Skip to content

Ensure our microbenchmarks are healthy and stay healthy across the repo #27607

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

Closed
javiercn opened this issue Nov 7, 2020 · 1 comment · Fixed by #29695
Closed

Ensure our microbenchmarks are healthy and stay healthy across the repo #27607

javiercn opened this issue Nov 7, 2020 · 1 comment · Fixed by #29695
Assignees
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework severity-nice-to-have This label is used by an internal tool
Milestone

Comments

@javiercn
Copy link
Member

javiercn commented Nov 7, 2020

Run 1 iteration of the microbenchmarks as part of the build process to ensure they work and the infrastructure is readily available when we need to work on performance.

@javiercn javiercn added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Nov 7, 2020
@dougbu
Copy link
Contributor

dougbu commented Nov 18, 2020

Including this in the DoI project for discussion in that context

@sebastienros you may be interested in this

@JunTaoLuo JunTaoLuo added the severity-nice-to-have This label is used by an internal tool label Dec 16, 2020
@BrennanConroy BrennanConroy self-assigned this Jan 20, 2021
@BrennanConroy BrennanConroy added this to the 6.0-preview2 milestone Jan 20, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework severity-nice-to-have This label is used by an internal tool
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants