[ABLD-474] Add flavor support to bazel test in dda inv test

[aiuto]

What does this PR do?

Add go tags based on flavor to bazel invocations inside dda inv test

Motivation

This makes the bazel test closer to equivalent to the go test.

Describe how you validated your changes

export EXPERIMENTAL_USE_BAZEL_TESTS=1

• dda inv test --targets=pkg/util
• Observe the bazel test command coming with the right go tags.

bazel cquery --@rules_go//go/config:tags=grpcnotrace,systemprobechecks,zstd,ec2,fargateprocess,oracle,sharedlibrarycheck,python,retrynotrace,trivy_no_javadb,clusterchecks,kubelet,ncm,orchestrator,zlib,otlp,zk,test,cel,no_dynamic_plugins,jmx,etcd,kubeapiserver,consul 'kind(go_test, //pkg/util/...)'
Found 101 Bazel-covered go_test targets
Skipping 101 Bazel-covered packages from go test
 ...
✓  pkg/util/kubernetes/clustername (5.656s)
✓  pkg/util/kubernetes/kubelet (6.28s)
✓  pkg/util/tags (6.482s)
✓  pkg/util/kubernetes/apiserver/controllers (6.593s)
✓  pkg/util/kubernetes/apiserver/leaderelection (11.741s)

DONE 369 tests in 11.770s
All tests passed
Unified test output written to ./test_output_unified.json
============================================================
  Test Report (unit) — PASSED
============================================================

311 total  311 passed  in 11.8s


============ Bazel tests ============
bazel test --keep_going --@rules_go//go/config:tags=grpcnotrace,systemprobechecks,zstd,ec2,fargateprocess,oracle,sharedlibrarycheck,python,retrynotrace,trivy_no_javadb,clusterchecks,kubelet,ncm,orchestrator,zlib,otlp,zk,test,cel,no_dynamic_plugins,jmx,etcd,kubeapiserver,consul //pkg/util/aggregatingqueue:aggregatingqueue_test //pkg/util/archive:archive_test //pkg/util/atomicstats:atomicstats_test //pkg/util/aws/creds:creds_test ....
...
DONE 101 tests in 135.610s
All tests passed

============================================================
  Test Report (unit + bazel) — PASSED
============================================================

412 total  406 passed  6 skipped  in 147.4s

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07815cc0c6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-official]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/datadog-agent | oracle: [21.3.0-xe]     

🛟 This job is unlikely to succeed on retry. Please review your pipeline configuration.

Failed to ping oracle instance: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.

ℹ️ Info

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 50.35% (-0.00%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 92d913f | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 6967b432:

Results for datadog-agent_7.81.0~devel.git.266.92d913f.pipeline.115448064-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 6967b43
📊 Static Quality Gates Dashboard
🔗 SQG Job

32 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	746.123 MiB
✅	agent_deb_amd64_fips	703.905 MiB
✅	agent_heroku_amd64	310.697 MiB
✅	agent_rpm_amd64	746.107 MiB
✅	agent_rpm_amd64_fips	703.889 MiB
✅	agent_rpm_arm64	723.684 MiB
✅	agent_rpm_arm64_fips	684.604 MiB
✅	agent_suse_amd64	746.107 MiB
✅	agent_suse_amd64_fips	703.889 MiB
✅	agent_suse_arm64	723.684 MiB
✅	agent_suse_arm64_fips	684.604 MiB
✅	docker_agent_amd64	806.283 MiB
✅	docker_agent_arm64	808.662 MiB
✅	docker_agent_jmx_amd64	997.203 MiB
✅	docker_agent_jmx_arm64	988.360 MiB
✅	docker_cluster_agent_amd64	207.082 MiB
✅	docker_cluster_agent_arm64	221.016 MiB
✅	docker_cws_instrumentation_amd64	7.154 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.499 MiB
✅	docker_dogstatsd_arm64	37.690 MiB
✅	docker_host_profiler_amd64	302.092 MiB
✅	docker_host_profiler_arm64	313.592 MiB
✅	dogstatsd_deb_amd64	30.155 MiB
✅	dogstatsd_deb_arm64	28.280 MiB
✅	dogstatsd_rpm_amd64	30.155 MiB
✅	dogstatsd_suse_amd64	30.155 MiB
✅	iot_agent_deb_amd64	44.468 MiB
✅	iot_agent_deb_arm64	41.437 MiB
✅	iot_agent_deb_armhf	42.150 MiB
✅	iot_agent_rpm_amd64	44.469 MiB
✅	iot_agent_suse_amd64	44.469 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 10919cf0-fca9-43e0-9a47-509ba768a85f

Baseline: 6967b43
Comparison: 92d913f
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+0.30	[-2.57, +3.17]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	ddot_metrics_sum_delta	memory utilization	+0.92	[+0.74, +1.09]	1	Logs
➖	docker_containers_cpu	% cpu utilization	+0.30	[-2.57, +3.17]	1	Logs
➖	ddot_logs	memory utilization	+0.16	[+0.11, +0.21]	1	Logs
➖	ddot_metrics	memory utilization	+0.09	[-0.10, +0.29]	1	Logs
➖	docker_containers_memory	memory utilization	+0.09	[-0.03, +0.22]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.09	[-0.93, +1.11]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.02	[-0.18, +0.23]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.02	[-0.38, +0.42]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.19, +0.21]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.10, +0.10]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.02	[-0.15, +0.10]	1	Logs
➖	quality_gate_idle	memory utilization	-0.03	[-0.08, +0.02]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.03	[-0.47, +0.41]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.04	[-0.53, +0.45]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.10	[-0.28, +0.09]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.11	[-0.35, +0.13]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	-0.19	[-0.24, -0.15]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.27	[-0.31, -0.23]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	-0.28	[-0.38, -0.19]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.32	[-0.37, -0.28]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.33	[-0.47, -0.18]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.39	[-0.62, -0.16]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.59	[-0.74, -0.44]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	721 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	245.33MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	722 ≥ 26
✅	file_to_blackhole_0ms_latency	memory_usage	10/10	0.16GiB ≤ 1.20GiB
✅	file_to_blackhole_0ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10	0.20GiB ≤ 1.20GiB
✅	file_to_blackhole_1000ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_100ms_latency	memory_usage	10/10	0.17GiB ≤ 1.20GiB
✅	file_to_blackhole_100ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_500ms_latency	memory_usage	10/10	0.18GiB ≤ 1.20GiB
✅	file_to_blackhole_500ms_latency	missed_bytes	10/10	0B = 0B
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	143.36MiB ≤ 147MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	740.74KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	474.73MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	182.54MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.34MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	343.85 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	384.03MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	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_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, 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 total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate 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.