[CWS] do not resolve new fields in functional test field collector

[paulcacheux]

What does this PR do?

When collecting fields values in the functional tests event collector, we might end up resolving fields that were not resolved during regular evaluation which is sub-optimal and could hide bugs (for example hashing files that were not hashed in the evaluation).

This PR tracks the fields that are resolved, and uses this to skip the resolution of fields that have not been evaluated.

This is a complete no-op outside of functional tests.

this reverts #31268

Motivation

Describe how to test/QA your changes

This is test debugging infrastructure.

Possible Drawbacks / Trade-offs

Additional Notes

[YoannGh]

Your PR should probably revert #31268 entirely

[agent-platform-auto-pr]

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=50138855 --os-family=ubuntu

Note: This applies to commit d421d18

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 15237371-5685-4506-92bc-e21c0940a871

Baseline: ae10a85
Comparison: d421d18
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	basic_py_check	% cpu utilization	+2.16	[-1.73, +6.05]	1	Logs
➖	quality_gate_logs	% cpu utilization	+1.64	[-1.34, +4.62]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.85	[+0.72, +0.98]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.60	[+0.54, +0.66]	1	Logs
➖	file_tree	memory utilization	+0.55	[+0.40, +0.70]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.54	[-0.24, +1.32]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.14	[-0.60, +0.88]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.06	[-0.72, +0.84]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.04	[-0.68, +0.75]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.08, +0.10]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.03	[-0.86, +0.81]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-0.08	[-3.52, +3.37]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.14	[-0.77, +0.49]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.14	[-0.84, +0.56]	1	Logs
➖	quality_gate_idle	memory utilization	-0.19	[-0.24, -0.14]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.35	[-0.80, +0.11]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	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	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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_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_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[spikat]

Should it be _functests.go instead of funtests.go?

[paulcacheux]

absolutely !

[paulcacheux]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-11-29 08:58:49 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2024-11-29 11:52:47 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 24m.

[paulcacheux]

/gitlab resync-job-status

[dd-devflow]

Devflow running: /gitlab resync-job-status

View all feedbacks in Devflow UI.

---

2024-11-29 10:54:36 UTC ℹ️ Devflow: /gitlab resync-job-status

297 jobs status updated and 229 skipped for a total of 526 jobs

[paulcacheux]

/gitlab resync-job-status

[dd-devflow]

Devflow running: /gitlab resync-job-status

View all feedbacks in Devflow UI.

---

2024-11-29 10:57:28 UTC ℹ️ Devflow: /gitlab resync-job-status

301 jobs status updated and 226 skipped for a total of 527 jobs