-
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] Decomission CircleCI #29463
base: main
Are you sure you want to change the base?
[CI] Decomission CircleCI #29463
Conversation
[Fast Unit Tests Report] On pipeline 44785165 (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: 170ad888-9804-4dc9-9b33-cfb1fbadda1d Metrics dashboard Target profiles Baseline: fa1af1c 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 |
---|---|---|---|---|---|---|
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.75 | [+0.70, +0.80] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | +0.40 | [-0.43, +1.23] | 1 | Logs |
➖ | idle | memory utilization | +0.31 | [+0.26, +0.35] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.00, +0.00] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | file_tree | memory utilization | -0.20 | [-0.31, -0.09] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.32 | [-2.08, -0.57] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -1.49 | [-4.04, +1.07] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -2.46 | [-5.27, +0.35] | 1 | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
❌ | idle | memory_usage | 9/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".
What does this PR do?
This PR removes all the former CircleCI jobs.
Motivation
We're migrating everything to Gitlab (or Github if the job is related to PR health).
go_linting
: already present here.licenses_linting
: added in #29331.copyrights_linting
: added in #29331.filename_linting
: added in #29331.shell_linting
: added in #29331.component_linting
: added in #29331.codeowner_linting
: added in #29331.build_binaries
: already present here for rtloader, here for the base Agent.build_iot_agent
: already present here.unit_tests
: already present here.integration_tests
: added in #29489.docker_tests
: added in #29489.Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes