[Backport 7.58.x] discovery: Allow delta for create time check

[agent-platform-auto-pr]

Backport f0c0ff4 from #29376.

---

What does this PR do?

The current time checks sometimes fail due to a one second diff in the expected and actual values.

The value returned by proc.CreateTime() can vary between invocations since the BootTime (used internally in proc.CreateTime()) can vary when the version of BootTimeWithContext which uses /proc/uptime is active in gopsutil (either on Docker, or even outside of it due to a bug fixed in v4.24.8: shirou/gopsutil@aa0b73d).

This is due to an inherent race since the code in BootTimeWithContext substracts the uptime of the host from the current time, and there can be in theory an unbounded amount of time between the read of /proc/uptime and the retrieval of the current time. Allow a 10 second diff as a reasonable value.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[pr-commenter]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=47967756 --os-family=ubuntu

Note: This applies to commit 6a20d12

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 33e1bea6-6074-4236-b026-8d39dbfc1d4e Metrics dashboard Target profiles

Baseline: 2e06337
Comparison: 6a20d12

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	file_tree	memory utilization	+1.05	[+0.92, +1.17]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.72	[-0.11, +1.55]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.60	[+0.54, +0.65]	1	Logs
➖	basic_py_check	% cpu utilization	+0.18	[-2.56, +2.93]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.05	[-0.70, +0.79]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	idle	memory utilization	-0.19	[-0.25, -0.14]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-1.36	[-3.96, +1.24]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
❌	idle	memory_usage	5/10

Explanation

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".

[vitkyrka]

/merge

[dd-devflow]

🚂 MergeQueue: pull request added to the queue

The median merge time in 7.58.x is 40m.

Use /merge -c to cancel this operation!