search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
15.42k stars 4.75k forks source link

Pull Requests CI Tests Holes Tracker #62276

Open marek-safar opened 2 years ago

marek-safar commented 2 years ago

This issue tracks rolling build (post PR merge) build and test failures caused by insufficient tests coverage during pull request CI build.

Broad impact:

Local impact:

@SamMonoRT @lewing @steveisok

dotnet-issue-labeler[bot] commented 2 years ago

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

ghost commented 2 years ago

Tagging subscribers to this area: @dotnet/runtime-infrastructure See info in area-owners.md if you want to be subscribed.

Issue Details
General tracker for issues that were caused by insufficient tests run during CI build - #61721 - #62081 @SamMonoRT @lewing @steveisok
Author: marek-safar
Assignees: -
Labels: `area-Infrastructure`, `untriaged`, `tracking`
Milestone: -
jkotas commented 2 years ago

cc @agocke

jkotas commented 2 years ago
danmoseley commented 2 years ago

What sorts of issues are we tracking here -- in principle any outerloop failure is a CI test hole. I assume this is about inner loop failures in configurations that didn't run before commit?

BTW it is not well defined whether "CI" means before or after commit so I avoid the term.

marek-safar commented 2 years ago

What sorts of issues are we tracking here

Update the description to be clearer.

in principle any outerloop failure is a CI test hole

Yes and I would include them here if they ever show up as a problem.