-
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
Bump docker/setup-buildx-action from 3.6.1 to 3.7.1 #29913
Bump docker/setup-buildx-action from 3.6.1 to 3.7.1 #29913
Conversation
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.6.1 to 3.7.1. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@988b5a0...c47758b) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
The following labels could not be found: |
[Fast Unit Tests Report] On pipeline 51095411 (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 ResultsMetrics dashboard Baseline: 39add53 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +2.33 | [+1.59, +3.07] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +1.49 | [+1.38, +1.60] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.15 | [+0.08, +0.22] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.12 | [-0.78, +1.02] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.10 | [-0.57, +0.78] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.03 | [-0.73, +0.79] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.10, +0.10] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.06 | [-0.52, +0.41] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.08 | [-0.93, +0.76] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.14 | [-0.90, +0.61] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.25 | [-0.89, +0.38] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.43 | [-0.47, -0.39] | 1 | Logs bounds checks dashboard |
➖ | otel_to_otel_logs | ingress throughput | -0.44 | [-1.13, +0.25] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.50 | [-1.28, +0.29] | 1 | Logs |
➖ | file_tree | memory utilization | -0.55 | [-0.67, -0.43] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -0.65 | [-3.57, +2.26] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | 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_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_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 | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
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_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, 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 memory_usage: 10/10 replicas passed. Gate passed.
/merge |
Devflow running:
|
…x-action-3.7.1
/merge |
Devflow running:
|
Package size comparisonComparison with ancestor Diff per package
Decision✅ Passed |
…x-action-3.7.1
/merge |
Devflow running:
|
Bumps docker/setup-buildx-action from 3.6.1 to 3.7.1.
Release notes
Sourced from docker/setup-buildx-action's releases.
Commits
c47758b
Merge pull request #369 from crazy-max/revert-crypto8fea382
chore: update generated content2874e98
switch back to uuid package8026d2b
Merge pull request #362 from docker/dependabot/npm_and_yarn/docker/actions-to...e51aab5
chore: update generated contentfd7390e
build(deps): bump@docker/actions-toolkit
from 0.35.0 to 0.39.0910a304
Merge pull request #366 from crazy-max/remove-uuid3623ee4
chore: update generated contente0e5ecf
remove uuid package and switch to crypto5334dd0
Merge pull request #363 from crazy-max/set-buildkitd-flags-optinYou can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)