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

Stop tagging the root module with 6.XX.0-devel #31608

Merged
merged 1 commit into from
Nov 29, 2024

Conversation

FlorentClarret
Copy link
Member

@FlorentClarret FlorentClarret commented Nov 29, 2024

What does this PR do?

Stop tagging the root module with 6.XX.0-devel

Motivation

This tag is not needed anymore on main

Describe how to test/QA your changes

Possible Drawbacks / Trade-offs

Additional Notes

@FlorentClarret FlorentClarret requested review from a team as code owners November 29, 2024 12:41
@FlorentClarret FlorentClarret changed the title Stop tagging the root module with 6.XX.0-devel Stop tagging the root module with 6.XX.0-devel Nov 29, 2024
@github-actions github-actions bot added short review PR is simple enough to be reviewed quickly team/agent-devx-loops team/agent-devx-infra labels Nov 29, 2024
@FlorentClarret FlorentClarret added changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation labels Nov 29, 2024
@FlorentClarret FlorentClarret force-pushed the florentclarret/devel-tag branch from 24c5c55 to ed950d6 Compare November 29, 2024 12:44
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Nov 29, 2024

[Fast Unit Tests Report]

On pipeline 50144801 (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

@FlorentClarret
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Nov 29, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-11-29 13:23:09 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 13:31:23 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 23m.

Copy link

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: f0fe9aa7-7025-45ab-9dbe-a306199d77fd

Baseline: 1b84417
Comparison: ed950d6
Diff

Optimization Goals: ❌ Significant changes detected

perf experiment goal Δ mean % Δ mean % CI trials links
pycheck_lots_of_tags % cpu utilization -8.48 [-11.87, -5.08] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
basic_py_check % cpu utilization +4.23 [+0.02, +8.44] 1 Logs
quality_gate_logs % cpu utilization +0.85 [-2.14, +3.83] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization +0.48 [-0.25, +1.21] 1 Logs
otel_to_otel_logs ingress throughput +0.45 [-0.21, +1.11] 1 Logs
tcp_syslog_to_blackhole ingress throughput +0.43 [+0.38, +0.48] 1 Logs
file_to_blackhole_300ms_latency egress throughput +0.30 [-0.33, +0.93] 1 Logs
quality_gate_idle memory utilization +0.30 [+0.25, +0.34] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.07 [-0.38, +0.53] 1 Logs
file_to_blackhole_100ms_latency egress throughput +0.07 [-0.59, +0.73] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.07 [-0.71, +0.84] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.03 [-0.81, +0.88] 1 Logs
file_to_blackhole_1000ms_latency egress throughput +0.03 [-0.74, +0.81] 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
quality_gate_idle_all_features memory utilization -0.37 [-0.46, -0.28] 1 Logs bounds checks dashboard
file_tree memory utilization -0.70 [-0.86, -0.55] 1 Logs
pycheck_lots_of_tags % cpu utilization -8.48 [-11.87, -5.08] 1 Logs

Bounds Checks: ❌ Failed

perf experiment bounds_check_name replicates_passed links
file_to_blackhole_100ms_latency lost_bytes 9/10
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 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, 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.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.

@dd-mergequeue dd-mergequeue bot merged commit 83ed39b into main Nov 29, 2024
203 of 204 checks passed
@dd-mergequeue dd-mergequeue bot deleted the florentclarret/devel-tag branch November 29, 2024 13:51
@github-actions github-actions bot added this to the 7.62.0 milestone Nov 29, 2024
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-devx-infra team/agent-devx-loops
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants