chore(ci): Bump docker/build-push-action from 5.4.0 to 6.2.0 #20748
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.4.0 to 6.2.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v5.4.0...v6.2.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
domain: ci
github-actions
bot
removed
the
domain: ci
Regression Detector ResultsRun ID: 42d6317b-81b8-4d6e-b5cf-7ea3720101b7 Metrics dashboard Baseline: 23b214b Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | links |
|---|---|---|---|---|---|
| ✅ | file_to_blackhole | egress throughput | +10.94 | [+3.36, +18.52] | |
| ➖ | syslog_humio_logs | ingress throughput | +2.07 | [+1.90, +2.23] | |
| ➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.86 | [+1.66, +2.07] | |
| ➖ | syslog_splunk_hec_logs | ingress throughput | +0.87 | [+0.76, +0.98] | |
| ➖ | syslog_loki | ingress throughput | +0.68 | [+0.61, +0.76] | |
| ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.62 | [+0.51, +0.73] | |
| ➖ | http_text_to_http_json | ingress throughput | +0.38 | [+0.26, +0.51] | |
| ➖ | fluent_elasticsearch | ingress throughput | +0.36 | [-0.12, +0.84] | |
| ➖ | http_elasticsearch | ingress throughput | +0.22 | [+0.09, +0.35] | |
| ➖ | otlp_grpc_to_blackhole | ingress throughput | +0.19 | [+0.08, +0.30] | |
| ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.11 | [+0.01, +0.21] | |
| ➖ | http_to_http_noack | ingress throughput | +0.11 | [+0.04, +0.17] | |
| ➖ | http_to_http_json | ingress throughput | +0.10 | [+0.04, +0.16] | |
| ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +0.07 | [-0.10, +0.24] | |
| ➖ | socket_to_socket_blackhole | ingress throughput | +0.04 | [-0.02, +0.09] | |
| ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.02 | [-0.06, +0.11] | |
| ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.11, +0.12] | |
| ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.00 | [-0.11, +0.11] | |
| ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.00 | [-0.10, +0.10] | |
| ➖ | syslog_log2metric_humio_metrics | ingress throughput | -0.20 | [-0.34, -0.07] | |
| ➖ | otlp_http_to_blackhole | ingress throughput | -0.25 | [-0.38, -0.12] | |
| ➖ | splunk_hec_route_s3 | ingress throughput | -0.40 | [-0.77, -0.04] | |
| ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.70 | [-0.83, -0.57] | |
| ➖ | http_to_s3 | ingress throughput | -0.78 | [-1.06, -0.50] | |
| ➖ | datadog_agent_remap_blackhole | ingress throughput | -1.34 | [-1.46, -1.22] | |
| ➖ | http_to_http_acks | ingress throughput | -1.45 | [-2.76, -0.14] |
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".
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Regression Detector ResultsRun ID: 7469b35a-9478-4c54-bf3b-08a60c87d2eb Metrics dashboard Baseline: ccb3a37 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 | links |
|---|---|---|---|---|---|
| ➖ | http_elasticsearch | ingress throughput | +1.73 | [+1.55, +1.91] | |
| ➖ | splunk_hec_route_s3 | ingress throughput | +1.73 | [+1.34, +2.12] | |
| ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +1.54 | [+1.35, +1.73] | |
| ➖ | fluent_elasticsearch | ingress throughput | +1.11 | [+0.62, +1.61] | |
| ➖ | http_text_to_http_json | ingress throughput | +0.62 | [+0.50, +0.74] | |
| ➖ | http_to_s3 | ingress throughput | +0.49 | [+0.21, +0.76] | |
| ➖ | otlp_grpc_to_blackhole | ingress throughput | +0.32 | [+0.21, +0.43] | |
| ➖ | syslog_splunk_hec_logs | ingress throughput | +0.09 | [-0.02, +0.20] | |
| ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.09 | [-0.06, +0.24] | |
| ➖ | syslog_loki | ingress throughput | +0.06 | [-0.02, +0.15] | |
| ➖ | http_to_http_json | ingress throughput | +0.06 | [+0.01, +0.11] | |
| ➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.02, +0.02] | |
| ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.11, +0.11] | |
| ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.00 | [-0.10, +0.10] | |
| ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.02 | [-0.10, +0.07] | |
| ➖ | http_to_http_acks | ingress throughput | -0.40 | [-1.72, +0.91] | |
| ➖ | datadog_agent_remap_blackhole | ingress throughput | -0.81 | [-0.93, -0.69] | |
| ➖ | socket_to_socket_blackhole | ingress throughput | -0.91 | [-0.95, -0.86] | |
| ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.05 | [-1.21, -0.90] | |
| ➖ | otlp_http_to_blackhole | ingress throughput | -1.13 | [-1.24, -1.03] | |
| ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -1.37 | [-1.49, -1.26] | |
| ➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.87 | [-2.01, -1.73] | |
| ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -2.14 | [-2.26, -2.02] | |
| ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -2.25 | [-2.46, -2.03] | |
| ➖ | syslog_humio_logs | ingress throughput | -2.54 | [-2.66, -2.42] | |
| ➖ | file_to_blackhole | egress throughput | -5.47 | [-12.04, +1.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".
jszwedko
deleted the
dependabot/github_actions/docker/build-push-action-6.2.0
branch
Bumps docker/build-push-action from 5.4.0 to 6.2.0.
Release notes
Sourced from docker/build-push-action's releases.
Commits
1556069Merge pull request #1158 from docker/dependabot/npm_and_yarn/docker/actions-t...57e1d34chore: update generated content309982echore(deps): Bump@docker/actions-toolkitfrom 0.27.0 to 0.28.09476c25Merge pull request #1153 from crazy-max/export-retention97be5a4chore: update generated content9cac6c8use default retention days for build export artifact31159d4Merge pull request #1149 from docker/dependabot/npm_and_yarn/docker/actions-t...07e1c3echore: update generated contentf7febd6chore(deps): Bump@docker/actions-toolkitfrom 0.26.2 to 0.27.0f6010eaMerge pull request #1147 from docker/dependabot/npm_and_yarn/docker/actions-t...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)