-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[ABLD-174] Make buildifier
work on Windows
#41213
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
[ABLD-174] Make buildifier
work on Windows
#41213
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 3d175ee Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
❌ | docker_containers_cpu | % cpu utilization | +13.76 | [+11.99, +15.54] | 1 | Logs |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
❌ | docker_containers_cpu | % cpu utilization | +13.76 | [+11.99, +15.54] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.66 | [+0.59, +0.73] | 1 | Logs |
➖ | quality_gate_metrics_logs | memory utilization | +0.62 | [+0.41, +0.82] | 1 | Logs bounds checks dashboard |
➖ | ddot_metrics_sum_delta | memory utilization | +0.29 | [+0.14, +0.44] | 1 | Logs |
➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.28 | [+0.08, +0.47] | 1 | Logs |
➖ | ddot_metrics_sum_cumulative | memory utilization | +0.06 | [-0.07, +0.19] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.05 | [-0.01, +0.12] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.58, +0.60] | 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.22, +0.20] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.02 | [-0.15, +0.10] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.03 | [-0.63, +0.58] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.03 | [-0.64, +0.58] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.08 | [-0.12, -0.03] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.11 | [-0.28, +0.06] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.13 | [-0.16, -0.09] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.19 | [-0.23, -0.16] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.20 | [-0.24, -0.16] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.23 | [-0.83, +0.37] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.38 | [-0.51, -0.25] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -2.26 | [-5.06, +0.54] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | -2.57 | [-3.00, -2.15] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | 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_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | memory_usage | 10/10 | bounds checks dashboard |
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:
-
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".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 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_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
ce938a4
to
0a469c7
Compare
f423559
to
85c3e9e
Compare
9f78461
to
970a959
Compare
ad3de9c
to
0260422
Compare
bc85124
to
0b06c80
Compare
0b06c80
to
9d45db3
Compare
bazel
settings on Windowsbuildifier
work on Windows
What does this PR do?
Applies 2 more patches that were submitted upstream:
exclude_patterns
on Windows too bazelbuild/buildtools#1399FINDSTR: Cannot open MANIFEST
bazelbuild/buildtools#1400Motivation
buildifier
macro: its implementation and Windows runner script template ignore excluded patterns as of today,buildifier_test
macro: the Windows runner script template doesn't consider thebazel
-provided manifest file.Describe how you validated your changes
Local Windows VM (QEMU/virt-manager).
Additional Notes
bazel run //bazel/buildifier
takes 2 minutes on Windows:buildifier
on modified files => again, later effort.