-
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
[system-probe] Add Oracle Linux to distros we install system-probe selinux policy on #29612
[system-probe] Add Oracle Linux to distros we install system-probe selinux policy on #29612
Conversation
[Fast Unit Tests Report] On pipeline 45321147 (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 |
d2e69a0
to
4f8d1dc
Compare
Regression DetectorRegression Detector ResultsRun ID: cc080f12-4dbe-4115-ae17-326352f0b630 Metrics dashboard Target profiles Baseline: 7fa44ed 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 |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.01 | [+0.27, +1.75] | 1 | Logs |
➖ | file_tree | memory utilization | +0.47 | [+0.38, +0.55] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | +0.45 | [-2.20, +3.10] | 1 | Logs |
➖ | idle | memory utilization | +0.30 | [+0.26, +0.34] | 1 | Logs |
➖ | idle_all_features | memory utilization | +0.04 | [-0.04, +0.12] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.09, +0.08] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.11 | [-0.16, -0.06] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -0.41 | [-2.90, +2.08] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.77 | [-1.57, +0.03] | 1 | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
✅ | idle | 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".
4f8d1dc
to
c46d768
Compare
/merge |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
…linux policy on (#29612)
…linux policy on (#29612)
What does this PR do?
Adds Oracle Linux to list of distros we install the system-probe selinux policy on.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes