Skip to content

Tracking flaky tests over time and driving the process towards fixing them. #27606

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
Closed
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

Comments

@javiercn
Copy link
Member

javiercn commented Nov 7, 2020

We used to have a tool that enabled us to see what tests were flaky in the product, get quick access to the failures and drive the investigation and fix process. This broke due to quota limits on the resources we were using. This issue tracks bringing that tracking in some shape or form for team members to use.

@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

Suggest this is actionable as PRs to https://runfo.azurewebsites.net/. @jaredpar where are the sources❔ Or, is there a planned move into, say, https://github.com/dotnet/arcade-services

Also, including this in the DoI project for discussion in that context.

@JunTaoLuo JunTaoLuo added the severity-nice-to-have This label is used by an internal tool label Dec 16, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 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

No branches or pull requests

3 participants