This is an automated backport of #6927: Fix flaky telemetry stats regression tests.
This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.
In #6907 we supposed to fix the telemetry stats regression test flakiness but unfortutanely it was not enough.
What happens is when the regression test runner setup the database for regression tests be executed we stop the scheduler and if for some reason a system job is running then it will be killed and it produces records on bgw_job_stat and bgw_job_stat_history with the crash information that can potentially lead to flaky test output.
To prevent it we cleanup system job stats metadata table just after stop the scheduler.
This is an automated backport of #6927: Fix flaky telemetry stats regression tests. This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.
For more details, please see the documentation
Original description
Fix flaky telemetry stats regression tests
In #6907 we supposed to fix the telemetry stats regression test flakiness but unfortutanely it was not enough.
What happens is when the regression test runner setup the database for regression tests be executed we stop the scheduler and if for some reason a system job is running then it will be killed and it produces records on
bgw_job_statandbgw_job_stat_historywith the crash information that can potentially lead to flaky test output.To prevent it we cleanup system job stats metadata table just after stop the scheduler.
Disable-check: force-changelog-file