Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Staging - [Alerting] Servicing Builds Running in R&D Pools Alert

See original GitHub issue

💔 Metric state changed to alerting

Please run the following query to identify the delinquent pipelines:

TimelineBuilds
| where QueueTime > ago(1d)
| where replace_string( Repository, '/','-') in ('dotnet-runtime', 'dotnet-arcade', 'dotnet-aspnetcore', 'dotnet-sdk', 'dotnet-winforms', 'dotnet-installer', 'dotnet-runtimelab', 'aspnet-Benchmarks', 'dotnet-templating', 'dotnet/fsharp', 'dotnet-release')
| where SourceBranch has 'release'
| join kind=inner (TimelineRecords
                    | where Order != 0
                    | where strlen(Path) == 11
                    | where WorkerName has 'NetCore1ESPool-' or WorkerName has 'NetCore-'
                    | where not(WorkerName has '-Svc')
                    | summarize arg_min(WorkerName, *) by RecordId, BuildId ) on BuildId

Go to rule

@dotnet/dnceng, please investigate

Automation information below, do not change

Grafana-Automated-Alert-Id-a5641c4a6d8e4e499f1710aa8386d81b

Issue Analytics

State:
Created 10 months ago
Comments:10 (9 by maintainers)

Top GitHub Comments

1reaction

jonfortescuecommented, Nov 23, 2022

oh nvm lol

0reactions

MattGalcommented, Nov 28, 2022

I think Matt has also said that so long as the main repos/big hitters are moved over, we are caring a bit less about this alert? I can’t remember. We’ll have to talk to Matt after the holiday.

This is correct, there’s just too many unusual special cases like release branches using Arcade main or “the ‘main’ branch has ‘release’ in the name” going on to make this rule actually reliable. I will check it out today though and see if there’s new places to move builds over.