Test: make plan-analysis probes heavy enough to rank in the top 50
Some checks are pending
CI / Build og unit tests (push) Waiting to run
CI / Integration (mcr.microsoft.com/mssql/server:2017-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2019-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2022-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2025-latest) (push) Blocked by required conditions

With SQL Agent and the whole suite running, three light executions did
not reach the 50 most CPU-heavy statements. The collector's behavior is
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E3EExwndy8Z22EK2Qpt6BK
This commit is contained in:
Claude 2026-09-29 07:56:46 +00:00
parent 15907401a9
commit d057b736ff
No known key found for this signature in database

View file

@ -244,7 +244,8 @@ public class CollectorTests(SqlServerFixture sql)
await using (var connection = new Microsoft.Data.SqlClient.SqlConnection(sql.DatabaseConnectionString(SqlServerFixture.TestDatabase)))
{
await connection.OpenAsync();
for (var i = 0; i < 3; i++)
// Enough executions to rank among the 50 heaviest statements even while the rest of the suite and SQL Agent run.
for (var i = 0; i < 60; i++)
{
await using var command = connection.CreateCommand();
command.CommandText = """