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

[ADXT-816] Dump e2e logs with failing / flaky categories #32653

Merged
merged 10 commits into from
Jan 10, 2025

Conversation

CelianR
Copy link
Contributor

@CelianR CelianR commented Jan 3, 2025

What does this PR do?

Splits e2e logs into four categories with the following priority (the higher the more priority it has):

  1. Failing / non flaky
  2. Failing / flaky
  3. Successful / non flaky
  4. Successful / flaky

If there is no more room to print a category, logs won't be printed so the more priority a category has, the more it has chance to appear on the logs.

In addition, a unit test is added to verify that tests are categorized.

Motivation

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

Example within a job log

Example with 2 non flaky tests and 1 flaky test.

Max size = 20:

WARNING: Too many logs to print, skipping logs printing to avoid Gitlab collapse. You can find your logs properly organized in the job artifacts: https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/None/artifacts/browse/e2e-output/logs/

Max size = 200:
Screenshot 2025-01-06 at 15 29 17

Max size = 2000:

Screenshot 2025-01-06 at 15 29 48

@CelianR CelianR added changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation team/agent-devx-infra labels Jan 3, 2025
@CelianR CelianR self-assigned this Jan 3, 2025
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Jan 3, 2025
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Jan 3, 2025

[Fast Unit Tests Report]

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

agent-platform-auto-pr bot commented Jan 3, 2025

Uncompressed package size comparison

Comparison with ancestor 20eef2836c876c9e9b24f0d185fcbc649ab8a86b

Diff per package
package diff status size ancestor threshold
datadog-agent-amd64-deb 0.00MB 1012.77MB 1012.77MB 0.50MB
datadog-agent-x86_64-rpm 0.00MB 1022.09MB 1022.09MB 0.50MB
datadog-agent-x86_64-suse 0.00MB 1022.09MB 1022.09MB 0.50MB
datadog-agent-arm64-deb 0.00MB 941.95MB 941.95MB 0.50MB
datadog-agent-aarch64-rpm 0.00MB 951.24MB 951.24MB 0.50MB
datadog-dogstatsd-amd64-deb 0.00MB 58.83MB 58.83MB 0.50MB
datadog-dogstatsd-x86_64-rpm 0.00MB 58.90MB 58.90MB 0.50MB
datadog-dogstatsd-x86_64-suse 0.00MB 58.90MB 58.90MB 0.50MB
datadog-dogstatsd-arm64-deb 0.00MB 56.33MB 56.33MB 0.50MB
datadog-heroku-agent-amd64-deb 0.00MB 506.57MB 506.57MB 0.50MB
datadog-iot-agent-amd64-deb 0.00MB 114.00MB 114.00MB 0.50MB
datadog-iot-agent-x86_64-rpm 0.00MB 114.07MB 114.07MB 0.50MB
datadog-iot-agent-x86_64-suse 0.00MB 114.07MB 114.07MB 0.50MB
datadog-iot-agent-arm64-deb 0.00MB 109.44MB 109.44MB 0.50MB
datadog-iot-agent-aarch64-rpm 0.00MB 109.51MB 109.51MB 0.50MB

Decision

✅ Passed

Copy link

cit-pr-commenter bot commented Jan 3, 2025

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 40e8eba6-71f9-4e2e-a694-ccf427fb9238

Baseline: 20eef28
Comparison: 2dbebfb
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +3.39 [+0.09, +6.69] 1 Logs
quality_gate_idle memory utilization +0.51 [+0.46, +0.55] 1 Logs bounds checks dashboard
file_to_blackhole_100ms_latency egress throughput +0.07 [-0.61, +0.76] 1 Logs
file_to_blackhole_0ms_latency_http1 egress throughput +0.04 [-0.78, +0.86] 1 Logs
file_to_blackhole_0ms_latency_http2 egress throughput +0.04 [-0.85, +0.93] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.02 [-0.76, +0.81] 1 Logs
file_to_blackhole_300ms_latency egress throughput +0.02 [-0.61, +0.65] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.00 [-0.12, +0.12] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
file_tree memory utilization -0.00 [-0.14, +0.13] 1 Logs
file_to_blackhole_0ms_latency egress throughput -0.04 [-0.96, +0.88] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -0.05 [-0.72, +0.62] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.23 [-0.30, -0.16] 1 Logs
file_to_blackhole_1000ms_latency_linear_load egress throughput -0.28 [-0.75, +0.19] 1 Logs
quality_gate_idle_all_features memory utilization -0.48 [-0.57, -0.39] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency egress throughput -0.64 [-1.43, +0.15] 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, bounds check memory_usage: 10/10 replicas passed. Gate 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.

@CelianR CelianR marked this pull request as ready for review January 7, 2025 09:19
@CelianR CelianR requested review from a team as code owners January 7, 2025 09:19
@CelianR CelianR changed the title [ADXT-816] Dump e2e logs [ADXT-816] Dump e2e logs with failing / flaky categories Jan 7, 2025
@CelianR CelianR added the ask-review Ask required teams to review this PR label Jan 7, 2025
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.

Very nice! Kudos for the PR description, screenshots help seeing what this results on

Copy link
Member

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

Cosmetic comments

tasks/new_e2e_tests.py Outdated Show resolved Hide resolved
tasks/new_e2e_tests.py Outdated Show resolved Hide resolved
tasks/new_e2e_tests.py Outdated Show resolved Hide resolved
@github-actions github-actions bot added medium review PR review might take time and removed short review PR is simple enough to be reviewed quickly labels Jan 8, 2025
@CelianR
Copy link
Contributor Author

CelianR commented Jan 9, 2025

/merge

@dd-devflow
Copy link

dd-devflow bot commented Jan 9, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-01-09 12:38:19 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.


2025-01-09 16:38:37 UTC ⚠️ MergeQueue: This merge request was unqueued

[email protected] unqueued this merge request: It did not become mergeable within the expected time

@CelianR
Copy link
Contributor Author

CelianR commented Jan 10, 2025

/merge

@dd-devflow
Copy link

dd-devflow bot commented Jan 10, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-01-10 08:35:39 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.


2025-01-10 09:32:41 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 35m.


2025-01-10 10:07:49 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit bdc78a5 into main Jan 10, 2025
212 checks passed
@dd-mergequeue dd-mergequeue bot deleted the celian/dump-logs-adxt-816 branch January 10, 2025 10:07
@github-actions github-actions bot added this to the 7.63.0 milestone Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ask-review Ask required teams to review this PR changelog/no-changelog medium review PR review might take time qa/no-code-change No code change in Agent code requiring validation team/agent-devx-infra
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants