[scheduler] do not wait for scheduling timer on stop

[masci]

When the Schedulers stops, jobs runners wait for the scheduling timer before evaluating the stop condition. This means if a check has a 180s interval, we need to wait three minutes until it stops.

[masci]

This could also be the reason why TestReload on scheduler's test suite is so flaky

[masci]

PR: #45

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a3bcec9a-f0b7-4c97-8f2c-2630668b5107

Baseline: 27e0032
Comparison: 2c70df1
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+3.99	[+1.14, +6.84]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+2.36	[+1.48, +3.25]	1	Logs
➖	otlp_ingest_logs	memory utilization	+1.05	[+0.93, +1.17]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.43	[+0.34, +0.51]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	+0.31	[+0.15, +0.48]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.10	[-0.54, +0.74]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.08	[-0.56, +0.71]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.03	[-0.60, +0.66]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.03	[-0.21, +0.26]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.01	[-0.62, +0.64]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.27, +0.27]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.02, +0.02]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.01	[-0.67, +0.66]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	-0.01	[-0.63, +0.61]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.01	[-0.59, +0.57]	1	Logs
➖	ddot_logs	memory utilization	-0.08	[-0.20, +0.04]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.15	[-0.20, -0.10]	1	Logs
➖	quality_gate_idle	memory utilization	-0.22	[-0.28, -0.16]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	-0.24	[-0.34, -0.15]	1	Logs
➖	file_tree	memory utilization	-0.48	[-0.60, -0.35]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-0.53	[-4.34, +3.27]	1	Logs
➖	ddot_metrics	memory utilization	-0.74	[-0.84, -0.64]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.05	[-1.10, -1.00]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.