You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had two recent failures (#66970 and https://github.com/dotnet/core-eng/issues/15594) when the pipeline was failing consistently and impacting all PRs.
However, that got missed because it does not submit passes/failures to test result database so the failures are hidden from many querying tools.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
Issue Details
We had two recent failures (#66970 and https://github.com/dotnet/core-eng/issues/15594) when the pipeline was failing consistently and impacting all PRs.
However, that got missed because it does not submit passes/failures to test result database so the failures are hidden from many querying tools.
Triage: We have similar needs to monitor Stress. We may not be able to achieve same DB as functional test results, but perhaps only one more place to look at and monitor.
Let's figure out if there is API in infra we could use -- as part of 7.0.
We had two recent failures (#66970 and https://github.com/dotnet/core-eng/issues/15594) when the pipeline was failing consistently and impacting all PRs.
However, that got missed because it does not submit passes/failures to test result database so the failures are hidden from many querying tools.
The text was updated successfully, but these errors were encountered: