-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 tokio-stream from 0.1.15 to 0.1.16 #21221
Conversation
Bumps [tokio-stream](https://github.com/tokio-rs/tokio) from 0.1.15 to 0.1.16. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-stream-0.1.15...tokio-stream-0.1.16) --- updated-dependencies: - dependency-name: tokio-stream dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Regression Detector ResultsRun ID: b3739cc5-5f03-4659-b2a6-f8c96ad85da4 Metrics dashboard Baseline: a1123c0 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 | +7.39 | [+0.27, +14.50] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | file_to_blackhole | egress throughput | +7.39 | [+0.27, +14.50] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +2.73 | [+2.64, +2.81] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +1.90 | [+1.77, +2.03] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +1.46 | [+1.37, +1.56] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +1.09 | [+0.93, +1.25] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.73 | [+0.63, +0.83] | |
➖ | splunk_hec_route_s3 | ingress throughput | +0.63 | [+0.32, +0.93] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.43 | [+0.33, +0.54] | |
➖ | socket_to_socket_blackhole | ingress throughput | +0.29 | [+0.22, +0.35] | |
➖ | http_to_http_noack | ingress throughput | +0.17 | [+0.09, +0.26] | |
➖ | http_to_http_json | ingress throughput | +0.04 | [-0.00, +0.09] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.02 | [-0.07, +0.12] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.01 | [-0.08, +0.09] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.11, +0.10] | |
➖ | otlp_http_to_blackhole | ingress throughput | -0.02 | [-0.14, +0.10] | |
➖ | syslog_humio_logs | ingress throughput | -0.07 | [-0.19, +0.05] | |
➖ | fluent_elasticsearch | ingress throughput | -0.13 | [-0.62, +0.35] | |
➖ | syslog_loki | ingress throughput | -0.34 | [-0.42, -0.26] | |
➖ | http_to_s3 | ingress throughput | -0.36 | [-0.63, -0.09] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.37 | [-0.55, -0.19] | |
➖ | http_to_http_acks | ingress throughput | -0.59 | [-1.85, +0.67] | |
➖ | http_text_to_http_json | ingress throughput | -0.87 | [-0.98, -0.75] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.00 | [-1.12, -0.87] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.11 | [-1.20, -1.02] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -1.37 | [-1.48, -1.26] | |
➖ | http_elasticsearch | ingress throughput | -2.26 | [-2.42, -2.11] |
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: ad659bd3-ba48-46fe-8a61-42321efb8e11 Metrics dashboard Baseline: 00ef42b 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 | -5.95 | [-12.89, +0.99] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | syslog_log2metric_humio_metrics | ingress throughput | +5.54 | [+5.41, +5.67] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +2.17 | [+2.05, +2.28] | |
➖ | syslog_humio_logs | ingress throughput | +1.54 | [+1.42, +1.66] | |
➖ | socket_to_socket_blackhole | ingress throughput | +1.19 | [+1.12, +1.26] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.07 | [+0.98, +1.15] | |
➖ | splunk_hec_route_s3 | ingress throughput | +1.01 | [+0.70, +1.33] | |
➖ | http_text_to_http_json | ingress throughput | +1.00 | [+0.90, +1.10] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.89 | [+0.76, +1.02] | |
➖ | http_to_http_acks | ingress throughput | +0.28 | [-1.00, +1.55] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +0.20 | [-0.02, +0.42] | |
➖ | http_to_s3 | ingress throughput | +0.10 | [-0.18, +0.37] | |
➖ | http_to_http_json | ingress throughput | +0.03 | [-0.01, +0.07] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.02 | [-0.07, +0.12] | |
➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.12, +0.11] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.09, +0.07] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.20 | [-0.31, -0.08] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.71 | [-0.90, -0.53] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.96 | [-1.05, -0.87] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.10 | [-1.20, -1.00] | |
➖ | fluent_elasticsearch | ingress throughput | -1.21 | [-1.69, -0.73] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.80 | [-1.90, -1.70] | |
➖ | otlp_http_to_blackhole | ingress throughput | -1.82 | [-1.94, -1.70] | |
➖ | http_elasticsearch | ingress throughput | -2.28 | [-2.46, -2.10] | |
➖ | syslog_loki | ingress throughput | -2.49 | [-2.56, -2.42] | |
➖ | file_to_blackhole | egress throughput | -5.95 | [-12.89, +0.99] |
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 tokio-stream from 0.1.15 to 0.1.16.
Commits
4ed0fa2
chore: prepare tokio-stream v0.1.16 (#6825)12b2567
chore: usepoll_fn
from std (#6810)35f244a
chore: prepare tokio-util v0.7.12 (#6823)1166ecc
config: enable full for tokio-util in the playground (#6818)27539ae
runtime: fix race in yield_defers_until_park test (#6809)ea6d652
chore: prepare Tokio v1.40.0 (#6806)11f66f4
chore: replaceready!
withstd::task::ready!
(#6804)479a56a
time: eliminate timer wheel allocations (#6779)b37f0de
runtime: implement initial set of task hooks (#6742)c9fad08
codec: fix typo in the docs forEncoder::Error
(#6800)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)