Lab / failure
Every session flagged itself RAN HOT
A check for noisy neighbours that couldn't find its own process, so every benchmark session reported itself as the noisy neighbour.
MeasurementWeftWeft's harness has a check for other processes eating CPU during a benchmark. The first version found its own row in ps by matching the binary's short name. For anything .NET, that name is just dotnet.
The string never matched, so the harness counted itself as an outsider, and every session flagged RAN HOT as soon as the benchmark used more than a quarter of a core. Which a benchmark does, on purpose.
A gate that's always red isn't a gate any more, just a constant with a colour. It matches on pid now.