-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 once_cell from 1.19.0 to 1.20.2 #21438
Conversation
7361200
to
145f8bf
Compare
Regression Detector ResultsRun ID: 91666195-ca25-4422-83f2-41b10613feb4 Metrics dashboard Baseline: f06da35 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 | -16.29 | [-22.56, -10.02] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | socket_to_socket_blackhole | ingress throughput | +5.39 | [+5.30, +5.49] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +4.48 | [+4.36, +4.59] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +4.24 | [+4.07, +4.41] | |
➖ | splunk_hec_route_s3 | ingress throughput | +3.32 | [+3.00, +3.64] | |
➖ | http_elasticsearch | ingress throughput | +2.35 | [+2.22, +2.48] | |
➖ | syslog_humio_logs | ingress throughput | +2.16 | [+2.02, +2.31] | |
➖ | otlp_http_to_blackhole | ingress throughput | +2.00 | [+1.85, +2.14] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.90 | [+1.69, +2.12] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.76 | [+1.63, +1.89] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.41 | [+1.29, +1.52] | |
➖ | syslog_loki | ingress throughput | +1.41 | [+1.24, +1.57] | |
➖ | http_text_to_http_json | ingress throughput | +1.15 | [+0.89, +1.40] | |
➖ | http_to_http_acks | ingress throughput | +0.97 | [-0.28, +2.21] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.83 | [+0.71, +0.95] | |
➖ | http_to_s3 | ingress throughput | +0.24 | [-0.04, +0.52] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.22 | [+0.11, +0.32] | |
➖ | http_to_http_noack | ingress throughput | +0.02 | [-0.02, +0.05] | |
➖ | http_to_http_json | ingress throughput | +0.01 | [-0.02, +0.04] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.09, +0.11] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.09, +0.08] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.21 | [-0.34, -0.08] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.76 | [-0.94, -0.59] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -1.30 | [-1.46, -1.15] | |
➖ | fluent_elasticsearch | ingress throughput | -2.32 | [-2.81, -1.82] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -2.61 | [-2.73, -2.49] | |
❌ | file_to_blackhole | egress throughput | -16.29 | [-22.56, -10.02] |
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".
145f8bf
to
cb78587
Compare
Dependabot attempted to update this pull request, but because the branch |
f893e8a
to
34eee9a
Compare
Bumps [once_cell](https://github.com/matklad/once_cell) from 1.19.0 to 1.20.2. - [Changelog](https://github.com/matklad/once_cell/blob/master/CHANGELOG.md) - [Commits](matklad/once_cell@v1.19.0...v1.20.2) --- updated-dependencies: - dependency-name: once_cell dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
34eee9a
to
aac81e3
Compare
Regression Detector ResultsRun ID: 54e1aa36-efe2-44b0-afb8-9ac86bab7795 Metrics dashboard Baseline: 31dc38f 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 | -7.73 | [-14.55, -0.90] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +2.40 | [+2.27, +2.54] | |
➖ | socket_to_socket_blackhole | ingress throughput | +2.24 | [+2.18, +2.30] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +1.91 | [+1.69, +2.13] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.74 | [+1.63, +1.84] | |
➖ | http_text_to_http_json | ingress throughput | +0.38 | [+0.27, +0.49] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.14 | [+0.04, +0.24] | |
➖ | http_to_http_noack | ingress throughput | +0.10 | [+0.03, +0.17] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +0.08 | [-0.05, +0.22] | |
➖ | syslog_loki | ingress throughput | +0.07 | [+0.01, +0.13] | |
➖ | http_to_http_json | ingress throughput | +0.05 | [+0.01, +0.10] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.02 | [-0.08, +0.12] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.10, +0.10] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.09, +0.08] | |
➖ | http_elasticsearch | ingress throughput | -0.04 | [-0.23, +0.14] | |
➖ | syslog_humio_logs | ingress throughput | -0.13 | [-0.24, -0.03] | |
➖ | splunk_hec_route_s3 | ingress throughput | -0.27 | [-0.57, +0.04] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.37 | [-0.47, -0.26] | |
➖ | http_to_s3 | ingress throughput | -0.62 | [-0.89, -0.35] | |
➖ | http_to_http_acks | ingress throughput | -0.80 | [-2.01, +0.42] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -1.00 | [-1.21, -0.80] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.33 | [-1.41, -1.24] | |
➖ | fluent_elasticsearch | ingress throughput | -1.77 | [-2.26, -1.29] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -1.98 | [-2.06, -1.90] | |
➖ | otlp_http_to_blackhole | ingress throughput | -3.64 | [-3.76, -3.52] | |
❌ | syslog_log2metric_humio_metrics | ingress throughput | -5.14 | [-5.26, -5.02] | |
❌ | file_to_blackhole | egress throughput | -7.73 | [-14.55, -0.90] |
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: 50729371-dda2-4fc7-95c6-0d359f49961d Metrics dashboard Baseline: 31dc38f 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 | +12.07 | [+4.68, +19.47] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | file_to_blackhole | egress throughput | +12.07 | [+4.68, +19.47] | |
➖ | socket_to_socket_blackhole | ingress throughput | +1.50 | [+1.43, +1.58] | |
➖ | splunk_hec_route_s3 | ingress throughput | +1.09 | [+0.78, +1.40] | |
➖ | syslog_humio_logs | ingress throughput | +0.70 | [+0.57, +0.84] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.64 | [+0.50, +0.79] | |
➖ | http_to_http_acks | ingress throughput | +0.46 | [-0.77, +1.68] | |
➖ | fluent_elasticsearch | ingress throughput | +0.42 | [-0.07, +0.92] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +0.33 | [+0.21, +0.44] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.29 | [+0.20, +0.39] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.26 | [+0.16, +0.36] | |
➖ | http_elasticsearch | ingress throughput | +0.22 | [+0.09, +0.36] | |
➖ | http_to_http_noack | ingress throughput | +0.20 | [+0.10, +0.29] | |
➖ | http_to_http_json | ingress throughput | +0.03 | [-0.01, +0.06] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.00 | [-0.09, +0.09] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.11, +0.10] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.02 | [-0.10, +0.06] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.04 | [-0.27, +0.19] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.52 | [-0.68, -0.36] | |
➖ | http_to_s3 | ingress throughput | -0.59 | [-0.86, -0.31] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -0.67 | [-0.75, -0.59] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.83 | [-0.91, -0.75] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.08 | [-1.17, -0.98] | |
➖ | syslog_loki | ingress throughput | -1.19 | [-1.28, -1.09] | |
➖ | otlp_http_to_blackhole | ingress throughput | -1.29 | [-1.43, -1.15] | |
➖ | http_text_to_http_json | ingress throughput | -2.52 | [-2.62, -2.43] | |
❌ | syslog_log2metric_humio_metrics | ingress throughput | -5.14 | [-5.25, -5.03] |
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: 56b3cf5b-0542-40cb-8894-5ea9c8505053 Metrics dashboard Baseline: 31dc38f 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 | -12.39 | [-18.96, -5.82] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +1.65 | [+1.53, +1.76] | |
➖ | http_text_to_http_json | ingress throughput | +1.51 | [+1.37, +1.64] | |
➖ | syslog_humio_logs | ingress throughput | +1.36 | [+1.23, +1.49] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.27 | [+1.09, +1.46] | |
➖ | fluent_elasticsearch | ingress throughput | +1.18 | [+0.68, +1.67] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.10 | [+0.98, +1.22] | |
➖ | socket_to_socket_blackhole | ingress throughput | +0.75 | [+0.68, +0.83] | |
➖ | splunk_hec_route_s3 | ingress throughput | +0.69 | [+0.39, +1.00] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +0.69 | [+0.59, +0.80] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +0.54 | [+0.39, +0.69] | |
➖ | http_to_http_noack | ingress throughput | +0.13 | [+0.05, +0.20] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.01 | [-0.07, +0.09] | |
➖ | http_to_http_json | ingress throughput | +0.01 | [-0.03, +0.05] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.10, +0.11] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.00 | [-0.10, +0.09] | |
➖ | http_to_s3 | ingress throughput | -0.10 | [-0.37, +0.17] | |
➖ | http_elasticsearch | ingress throughput | -0.10 | [-0.28, +0.07] | |
➖ | syslog_loki | ingress throughput | -0.34 | [-0.41, -0.27] | |
➖ | http_to_http_acks | ingress throughput | -1.12 | [-2.33, +0.10] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -1.16 | [-1.27, -1.06] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -1.20 | [-1.29, -1.12] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.36 | [-1.47, -1.25] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -1.54 | [-1.66, -1.43] | |
➖ | otlp_http_to_blackhole | ingress throughput | -2.77 | [-2.90, -2.64] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -3.62 | [-3.75, -3.49] | |
❌ | file_to_blackhole | egress throughput | -12.39 | [-18.96, -5.82] |
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 once_cell from 1.19.0 to 1.20.2.
Changelog
Sourced from once_cell's changelog.
Commits
4fbd4a5
release 1.20.30aef2f8
Merge pull request #267 from taiki-e/portable-atomiccf87ac6
Remove "portable-atomic?/require-cas" from race feature3b9bd9b
release 1.20.1f61508a
Merge pull request #265 from taiki-e/portable-atomic449e5d7
Add portable-atomic feature and disable portable-atomic/critical-section by d...72f7c2e
Merge pull request #260 from brodycj/propagate-critical-section-to-portable-a...be6b623
v1.20.0f2d95bf
update Cargo (dev-)dependencies; update Cargo.lock.msrvdd6b5c2
ci: fix TEST_BETA with TEMPORARY WORKAROUND in RUSTFLAGSDependabot 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)