-
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
fix(fetch_secret): Transfer the exit code in windows context #30031
base: main
Are you sure you want to change the base?
Conversation
Currently when facing an `Unable to locate` credential issue on windows we are not using the `retry:exit_codes`. To do so we need to transfer the $lastExitCode up to the Gitlab script
Gitlab CI Configuration Changes
|
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 11 | 0 | 0 |
ℹ️ Diff available in the job log.
[Fast Unit Tests Report] On pipeline 46318419 (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: c6bcefc2-e2be-4d69-868a-c6af029bee9f Metrics dashboard Target profiles Baseline: 8938f60 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 |
---|---|---|---|---|---|---|
➖ | idle_all_features | memory utilization | +1.43 | [+1.30, +1.55] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.83 | [+0.78, +0.89] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | +0.67 | [-0.13, +1.48] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.31 | [-0.18, +0.80] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.30 | [-0.43, +1.03] | 1 | Logs |
➖ | idle | memory utilization | +0.08 | [+0.02, +0.14] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.06 | [-0.12, +0.23] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.02 | [-0.23, +0.26] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.32, +0.34] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.11, +0.11] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.23, +0.22] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -0.23 | [-2.67, +2.21] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -0.62 | [-3.28, +2.05] | 1 | Logs |
➖ | file_tree | memory utilization | -0.65 | [-0.79, -0.50] | 1 | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
❌ | file_to_blackhole_1000ms_latency | memory_usage | 0/10 |
❌ | file_to_blackhole_300ms_latency | memory_usage | 0/10 |
❌ | file_to_blackhole_500ms_latency | memory_usage | 0/10 |
❌ | idle | memory_usage | 6/10 |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 |
✅ | 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".
What does this PR do?
Currently when facing an
Unable to locate
credential issue on windows we are not using theretry:exit_codes
. To do so we need to transfer the $lastExitCode up to the Gitlab scriptMotivation
Have an automatic retry in this situation
Describe how to test/QA your changes
TBD
Possible Drawbacks / Trade-offs
Additional Notes