Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

omnibus: fix false positive when forcing omnibus versions through env #32466

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

chouquette
Copy link
Contributor

What does this PR do?

Account for omnibus ruby & software versions being forced through the environment

Motivation

This fixes a potential false positive when computing the cache key for omnibus-ruby & omnibus-software child pipeline.
An example can be found here: https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/748313477

This is not a critical problem since omnibus will realize the recipe changed, but it will upload the updated cache, which will in turn cause a more complete build than is necessary for other pipelines using this cache key.

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

@chouquette chouquette added changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation team/agent-delivery labels Dec 23, 2024
@chouquette chouquette requested a review from a team as a code owner December 23, 2024 15:41
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Dec 23, 2024
Copy link
Contributor

@Pythyu Pythyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch 👍

@chouquette
Copy link
Contributor Author

We currently exclude OMNIBUS_ variables when computing the cache key, we could also remove them from the exclusion list, but I think keeping these 2 variables tied to it's actual meaning is a cleanest approach.
I'm open to discussions about this :)

@Pythyu
Copy link
Contributor

Pythyu commented Dec 23, 2024

I agree, I think it makes the most sense to keep them

@agent-platform-auto-pr
Copy link
Contributor

[Fast Unit Tests Report]

On pipeline 51736585 (CI Visibility). The following jobs did not run any unit tests:

Jobs:
  • tests_deb-arm64-py3
  • tests_deb-x64-py3
  • tests_flavor_dogstatsd_deb-x64
  • tests_flavor_heroku_deb-x64
  • tests_flavor_iot_deb-x64
  • tests_rpm-arm64-py3
  • tests_rpm-x64-py3
  • tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

@agent-platform-auto-pr
Copy link
Contributor

Uncompressed package size comparison

Comparison with ancestor 7e9cb15c5c8ca87cea9c2aeffbed701c8901a678

Diff per package
package diff status size ancestor threshold
datadog-heroku-agent-amd64-deb 1.40MB ⚠️ 506.49MB 505.09MB 70.00MB
datadog-agent-aarch64-rpm 0.01MB ⚠️ 943.35MB 943.34MB 140.00MB
datadog-agent-arm64-deb 0.01MB ⚠️ 934.11MB 934.09MB 140.00MB
datadog-dogstatsd-amd64-deb 0.00MB 78.57MB 78.57MB 10.00MB
datadog-dogstatsd-x86_64-rpm 0.00MB 78.65MB 78.65MB 10.00MB
datadog-dogstatsd-x86_64-suse 0.00MB 78.65MB 78.65MB 10.00MB
datadog-dogstatsd-arm64-deb 0.00MB 55.77MB 55.77MB 10.00MB
datadog-iot-agent-amd64-deb 0.00MB 113.34MB 113.34MB 10.00MB
datadog-iot-agent-x86_64-rpm 0.00MB 113.41MB 113.41MB 10.00MB
datadog-iot-agent-x86_64-suse 0.00MB 113.41MB 113.41MB 10.00MB
datadog-iot-agent-arm64-deb 0.00MB 108.81MB 108.81MB 10.00MB
datadog-iot-agent-aarch64-rpm 0.00MB 108.88MB 108.88MB 10.00MB
datadog-agent-x86_64-rpm -0.00MB 1197.45MB 1197.46MB 140.00MB
datadog-agent-x86_64-suse -0.00MB 1197.45MB 1197.46MB 140.00MB
datadog-agent-amd64-deb -0.01MB 1188.19MB 1188.19MB 140.00MB

Decision

⚠️ Warning

Copy link

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 68897973-fde9-4192-afc2-38cd804e9ed9

Baseline: 7e9cb15
Comparison: 9107ea7
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
uds_dogstatsd_to_api_cpu % cpu utilization +0.83 [+0.14, +1.52] 1 Logs
otel_to_otel_logs ingress throughput +0.52 [-0.20, +1.23] 1 Logs
file_tree memory utilization +0.46 [+0.34, +0.59] 1 Logs
file_to_blackhole_1000ms_latency egress throughput +0.13 [-0.65, +0.91] 1 Logs
file_to_blackhole_0ms_latency_http1 egress throughput +0.11 [-0.76, +0.98] 1 Logs
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.11 [-0.35, +0.57] 1 Logs
file_to_blackhole_300ms_latency egress throughput +0.06 [-0.58, +0.70] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.05 [-0.73, +0.83] 1 Logs
quality_gate_idle_all_features memory utilization +0.04 [-0.04, +0.12] 1 Logs bounds checks dashboard
file_to_blackhole_100ms_latency egress throughput +0.02 [-0.73, +0.77] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.01 [-0.12, +0.13] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.00 [-0.86, +0.86] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
file_to_blackhole_0ms_latency_http2 egress throughput -0.06 [-0.91, +0.80] 1 Logs
quality_gate_idle memory utilization -0.29 [-0.33, -0.25] 1 Logs bounds checks dashboard
quality_gate_logs % cpu utilization -0.31 [-3.47, +2.84] 1 Logs
tcp_syslog_to_blackhole ingress throughput -2.34 [-2.42, -2.27] 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_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 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_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.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

@chouquette
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Jan 6, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-01-06 10:27:41 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 35m.


2025-01-06 11:01:56 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit 85f8b10 into main Jan 6, 2025
244 checks passed
@dd-mergequeue dd-mergequeue bot deleted the chouquette/omnibus_cache_false_positive branch January 6, 2025 11:01
@github-actions github-actions bot added this to the 7.63.0 milestone Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-delivery
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants