-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[CI] Fix Python virtualenv usage in the Gitlab macOS runners #30612
Conversation
Gitlab CI Configuration Changes
|
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 7 | 3 | 0 |
ℹ️ Diff available in the job log.
[Fast Unit Tests Report] On pipeline 47967460 (CI Visibility). The following jobs did not run any unit tests: Jobs:
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 |
Regression DetectorRegression Detector ResultsRun ID: e3f4f341-cd15-4a00-b6d8-1941f06c747c Metrics dashboard Target profiles Baseline: 0a57140 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | pycheck_lots_of_tags | % cpu utilization | +1.16 | [-1.40, +3.71] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.31 | [+0.26, +0.37] | 1 | Logs |
➖ | file_tree | memory utilization | +0.17 | [+0.02, +0.31] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.04 | [-0.29, +0.37] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.02 | [-0.10, +0.14] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | idle | memory utilization | -0.00 | [-0.06, +0.05] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.01 | [-0.25, +0.24] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.23, +0.22] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.02 | [-0.21, +0.16] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.07 | [-0.56, +0.42] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.28 | [-1.09, +0.53] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.96 | [-1.01, -0.91] | 1 | Logs bounds checks dashboard |
➖ | basic_py_check | % cpu utilization | -0.99 | [-3.84, +1.87] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.71 | [-2.44, -0.97] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -2.01 | [-2.14, -1.88] | 1 | Logs bounds checks dashboard |
➖ | idle_all_features | memory utilization | -2.38 | [-2.50, -2.26] | 1 | Logs bounds checks dashboard |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 |
✅ | idle | memory_usage | 10/10 |
✅ | idle_all_features | memory_usage | 10/10 |
✅ | quality_gate_idle | memory_usage | 10/10 |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 |
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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
Its configuration does not mark it "erratic".
This reverts commit 48b1d5b.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What a proper gitlab syntax 👀
/merge |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes