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

add CI visibility links to KMT run jobs #26948

Merged
merged 6 commits into from
Jun 21, 2024

Conversation

brycekahle
Copy link
Member

What does this PR do?

  • add CI visibility links to KMT run jobs
  • add direct links to test runs

Motivation

Easier pivot to CI Visibility product

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

@brycekahle brycekahle added changelog/no-changelog team/ebpf-platform qa/done Skip QA week as QA was done before merge and regressions are covered by tests labels Jun 20, 2024
@brycekahle brycekahle added this to the 7.56.0 milestone Jun 20, 2024
@brycekahle brycekahle requested review from a team as code owners June 20, 2024 19:56
@pr-commenter
Copy link

pr-commenter bot commented Jun 20, 2024

Regression Detector

Regression Detector Results

Run ID: d574a32a-fa84-49cb-b9b9-56405edcb8a1 Metrics dashboard Target profiles

Baseline: 79aaadb
Comparison: d1a725b

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 links
tcp_syslog_to_blackhole ingress throughput +1.94 [-11.12, +15.00] Logs
idle memory utilization +0.56 [+0.53, +0.60] Logs
uds_dogstatsd_to_api ingress throughput +0.00 [-0.00, +0.00] Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.01, +0.01] Logs
file_tree memory utilization -0.11 [-0.15, -0.06] Logs
pycheck_1000_100byte_tags % cpu utilization -0.42 [-5.20, +4.36] Logs
otel_to_otel_logs ingress throughput -0.44 [-1.25, +0.37] Logs
uds_dogstatsd_to_api_cpu % cpu utilization -0.56 [-1.45, +0.33] Logs
basic_py_check % cpu utilization -1.16 [-3.85, +1.52] Logs

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

Copy link
Contributor

@pducolin pducolin left a comment

Choose a reason for hiding this comment

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

Minor comment on the URL names, might be confusing since product name split event if the base URL is the same

tasks/gitlab_helpers.py Outdated Show resolved Hide resolved
tasks/gitlab_helpers.py Outdated Show resolved Hide resolved
Copy link
Contributor

@chouetz chouetz left a comment

Choose a reason for hiding this comment

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

Minor comments, nothing to prevent merge

tasks/gitlab_helpers.py Outdated Show resolved Hide resolved
tasks/gitlab_helpers.py Outdated Show resolved Hide resolved
}
},
]
}


def get_link_to_job_id(job_id: str):
def get_link_to_pipeline_job_id(job_id: str):
query_params = {
"ci_level": "job",
"@ci.job.id": job_id,
"@ci.pipeline.name": "DataDog/datadog-agent",
}
query_string = to_query_string(query_params)
Copy link
Contributor

Choose a reason for hiding this comment

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

why don't we use urllib.parse.urlencode here? It's normally already quoted

Copy link
Member Author

Choose a reason for hiding this comment

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

I think because the entire string is a query value, so characters like & need to be encoded too.

Copy link
Contributor

Choose a reason for hiding this comment

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

From urllib.parse.urlencode

An alternate function that can be passed as quote_via is quote(), which will encode spaces as %20 and not encode ‘/’ characters. For maximum control of what is quoted, use quote and specify a value for safe.

I could use quote(urlencode(query_params)), didn't know it!

def get_link_to_test_runs(job_id: str):
query_params = {
"test_level": "test",
"@ci.job.url": f"\"https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/{job_id}\"",
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we use job.name and git.branch instead? It's not strictly similar if you have several executions on the same branch so maybe the commit id. It's then easier to navigate in ci-vis I guess

Copy link
Member Author

Choose a reason for hiding this comment

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

If you retry a job in Gitlab, it will have a different ID but the branch, commit, and job name will remain the same.

Copy link
Contributor

Choose a reason for hiding this comment

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

CI Test Vis executions miss the ci.job.id, I asked for it

@agent-platform-auto-pr
Copy link
Contributor

[Fast Unit Tests Report]

On pipeline 37339878 (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-developer-experience

@brycekahle
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Jun 21, 2024

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 34m.

Use /merge -c to cancel this operation!

@dd-mergequeue dd-mergequeue bot merged commit 2ff3c92 into main Jun 21, 2024
298 of 299 checks passed
@dd-mergequeue dd-mergequeue bot deleted the bryce.kahle/ci-visibility-links branch June 21, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog qa/done Skip QA week as QA was done before merge and regressions are covered by tests team/ebpf-platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants