-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(deps): Bump cargo-lock from 9.0.0 to 10.0.0 #21518
Conversation
Bumps [cargo-lock](https://github.com/RustSec/rustsec) from 9.0.0 to 10.0.0. - [Release notes](https://github.com/RustSec/rustsec/releases) - [Commits](rustsec/rustsec@cargo-lock/v9.0.0...cargo-lock/v10.0.0) --- updated-dependencies: - dependency-name: cargo-lock dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Regression Detector ResultsRun ID: cd1061b3-3f72-429b-9bdd-1c9089693881 Metrics dashboard Baseline: cd8039d 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 | +0.78 | [-3.30, +4.85] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | datadog_agent_remap_blackhole | ingress throughput | +8.99 | [+8.62, +9.36] | |
➖ | syslog_humio_logs | ingress throughput | +4.06 | [+3.78, +4.34] | |
➖ | fluent_elasticsearch | ingress throughput | +2.98 | [+2.41, +3.54] | |
➖ | splunk_hec_route_s3 | ingress throughput | +2.97 | [+2.67, +3.28] | |
➖ | syslog_loki | ingress throughput | +1.34 | [+1.23, +1.44] | |
➖ | file_to_blackhole | egress throughput | +0.78 | [-3.30, +4.85] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.55 | [+0.39, +0.71] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.45 | [+0.37, +0.54] | |
➖ | otlp_http_to_blackhole | ingress throughput | +0.29 | [+0.21, +0.38] | |
➖ | http_text_to_http_json | ingress throughput | +0.12 | [-0.22, +0.47] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +0.06 | [-0.14, +0.26] | |
➖ | http_to_http_acks | ingress throughput | +0.02 | [-0.47, +0.51] | |
➖ | http_to_http_json | ingress throughput | +0.00 | [-0.04, +0.05] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | http_to_http_noack | ingress throughput | -0.01 | [-0.06, +0.04] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.04, +0.01] | |
➖ | http_to_s3 | ingress throughput | -0.21 | [-0.39, -0.02] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.64 | [-0.84, -0.44] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.06 | [-1.23, -0.90] | |
➖ | socket_to_socket_blackhole | ingress throughput | -1.10 | [-1.20, -0.99] | |
➖ | http_elasticsearch | ingress throughput | -3.33 | [-3.54, -3.11] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -3.43 | [-3.65, -3.20] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -3.94 | [-4.20, -3.69] | |
❌ | syslog_log2metric_humio_metrics | ingress throughput | -7.06 | [-7.37, -6.75] | |
❌ | syslog_splunk_hec_logs | ingress throughput | -7.99 | [-8.33, -7.66] |
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".
Regression Detector ResultsRun ID: e7b413a6-01c9-40d1-986a-80ebf930f83d Metrics dashboard Baseline: b39acf2 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 | -0.86 | [-5.03, +3.31] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | http_text_to_http_json | ingress throughput | +5.37 | [+5.13, +5.62] | |
➖ | socket_to_socket_blackhole | ingress throughput | +3.50 | [+3.28, +3.73] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +3.47 | [+3.21, +3.73] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +2.50 | [+2.30, +2.71] | |
➖ | splunk_hec_route_s3 | ingress throughput | +1.66 | [+1.33, +1.99] | |
➖ | http_to_s3 | ingress throughput | +1.36 | [+1.20, +1.52] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.10 | [+0.92, +1.28] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.81 | [+0.75, +0.86] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.76 | [+0.66, +0.85] | |
➖ | syslog_humio_logs | ingress throughput | +0.75 | [+0.52, +0.97] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +0.16 | [+0.03, +0.30] | |
➖ | http_to_http_json | ingress throughput | +0.01 | [-0.03, +0.06] | |
➖ | http_to_http_noack | ingress throughput | +0.01 | [-0.05, +0.06] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.00 | [-0.02, +0.02] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.03 | [-0.21, +0.15] | |
➖ | http_to_http_acks | ingress throughput | -0.04 | [-0.53, +0.45] | |
➖ | fluent_elasticsearch | ingress throughput | -0.22 | [-0.74, +0.30] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.35 | [-0.49, -0.21] | |
➖ | syslog_loki | ingress throughput | -0.52 | [-0.61, -0.43] | |
➖ | file_to_blackhole | egress throughput | -0.86 | [-5.03, +3.31] | |
➖ | otlp_http_to_blackhole | ingress throughput | -0.97 | [-1.15, -0.79] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.04 | [-1.25, -0.83] | |
➖ | http_elasticsearch | ingress throughput | -1.14 | [-1.38, -0.89] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.73 | [-2.08, -1.37] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | -2.49 | [-2.57, -2.41] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -2.92 | [-3.17, -2.67] |
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".
Regression Detector ResultsRun ID: 348d0144-a78d-4bff-9628-f19dc68fb11f Metrics dashboard Baseline: 2883ca7 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 |
---|---|---|---|---|---|
➖ | file_to_blackhole | egress throughput | +1.91 | [-2.21, +6.02] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | splunk_hec_route_s3 | ingress throughput | +3.84 | [+3.54, +4.13] | |
➖ | http_elasticsearch | ingress throughput | +2.15 | [+1.98, +2.31] | |
➖ | file_to_blackhole | egress throughput | +1.91 | [-2.21, +6.02] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +1.78 | [+1.68, +1.88] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.70 | [+1.53, +1.86] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.62 | [+1.55, +1.69] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.31 | [+1.12, +1.50] | |
➖ | syslog_loki | ingress throughput | +0.95 | [+0.88, +1.02] | |
➖ | http_text_to_http_json | ingress throughput | +0.88 | [+0.77, +0.99] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.58 | [+0.48, +0.67] | |
➖ | socket_to_socket_blackhole | ingress throughput | +0.28 | [+0.23, +0.34] | |
➖ | otlp_http_to_blackhole | ingress throughput | +0.27 | [+0.16, +0.38] | |
➖ | syslog_humio_logs | ingress throughput | +0.20 | [+0.10, +0.31] | |
➖ | http_to_http_json | ingress throughput | +0.00 | [-0.05, +0.06] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | http_to_http_noack | ingress throughput | -0.00 | [-0.06, +0.05] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.02 | [-0.04, +0.01] | |
➖ | http_to_http_acks | ingress throughput | -0.06 | [-0.55, +0.43] | |
➖ | http_to_s3 | ingress throughput | -0.10 | [-0.27, +0.07] | |
➖ | fluent_elasticsearch | ingress throughput | -0.20 | [-0.74, +0.34] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.28 | [-0.39, -0.16] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.43 | [-0.60, -0.26] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -0.44 | [-0.54, -0.35] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.47 | [-1.65, -1.30] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.75 | [-1.89, -1.61] |
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".
Bumps cargo-lock from 9.0.0 to 10.0.0.
Commits
4080f21
cargo-lock v10.0.0 (#1264)f2d4193
cargo-lock: usedoc_auto_cfg
(#1263)d7d39fc
cargo-audit: bumpabscissa
to v0.8 (#1262)2623e6f
Merge pull request #1261 from Shnatsel/bump-auditable-extract470ff93
Bump auditable-extract in Cargo.lock for the WASM bugfix463253b
build(deps): bump actions/cache from 4.1.0 to 4.1.1 (#1259)fc8d206
V4 is supported now (#1260)d1d0fce
rustsec v0.30.0-rc.0 (#1258)bd0e3c3
cargo-lock v10.0.0-rc.0 (#1257)feeb220
cargo-lock: add support for V4 lockfiles (#1206)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 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)