-
Notifications
You must be signed in to change notification settings - Fork 2k
chore(deps): Bump libc from 0.2.154 to 0.2.155 #20523
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
Conversation
|
Dependabot attempted to update this pull request, but because the branch |
Bumps [libc](https://github.com/rust-lang/libc) from 0.2.154 to 0.2.155. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](rust-lang/libc@0.2.154...0.2.155) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
d59b7dd to
e577684
Compare
Regression Detector ResultsRun ID: 3bae1d29-19e3-42af-b510-e7ddb22f4e60 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 |
|---|---|---|---|---|
| ➖ | http_to_http_acks | ingress throughput | +2.37 | [+1.00, +3.74] |
| ➖ | otlp_http_to_blackhole | ingress throughput | +1.57 | [+1.43, +1.70] |
| ➖ | syslog_humio_logs | ingress throughput | +1.39 | [+1.26, +1.51] |
| ➖ | socket_to_socket_blackhole | ingress throughput | +0.93 | [+0.85, +1.02] |
| ➖ | fluent_elasticsearch | ingress throughput | +0.18 | [-0.31, +0.66] |
| ➖ | http_elasticsearch | ingress throughput | +0.17 | [+0.09, +0.25] |
| ➖ | file_to_blackhole | egress throughput | +0.11 | [-2.37, +2.60] |
| ➖ | http_to_http_noack | ingress throughput | +0.08 | [-0.01, +0.18] |
| ➖ | http_to_http_json | ingress throughput | +0.07 | [-0.01, +0.15] |
| ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.14, +0.14] |
| ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.15, +0.14] |
| ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.03 | [-0.14, +0.09] |
| ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.07 | [-0.18, +0.04] |
| ➖ | enterprise_http_to_http | ingress throughput | -0.10 | [-0.17, -0.03] |
| ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.13 | [-0.21, -0.04] |
| ➖ | syslog_splunk_hec_logs | ingress throughput | -0.15 | [-0.21, -0.09] |
| ➖ | http_to_s3 | ingress throughput | -0.18 | [-0.46, +0.10] |
| ➖ | otlp_grpc_to_blackhole | ingress throughput | -0.23 | [-0.32, -0.14] |
| ➖ | http_text_to_http_json | ingress throughput | -0.32 | [-0.45, -0.19] |
| ➖ | datadog_agent_remap_blackhole | ingress throughput | -0.72 | [-0.83, -0.62] |
| ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.90 | [-1.03, -0.77] |
| ➖ | syslog_loki | ingress throughput | -1.15 | [-1.22, -1.08] |
| ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.34 | [-1.54, -1.14] |
| ➖ | splunk_hec_route_s3 | ingress throughput | -1.71 | [-2.17, -1.26] |
| ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -1.77 | [-1.90, -1.64] |
| ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -3.12 | [-3.30, -2.95] |
| ➖ | syslog_log2metric_humio_metrics | ingress throughput | -4.11 | [-4.22, -3.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 [libc](https://github.com/rust-lang/libc) from 0.2.154 to 0.2.155. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](rust-lang/libc@0.2.154...0.2.155) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [libc](https://github.com/rust-lang/libc) from 0.2.154 to 0.2.155. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](rust-lang/libc@0.2.154...0.2.155) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps libc from 0.2.154 to 0.2.155.
Release notes
Sourced from libc's releases.
Commits
7df63bdMerge pull request #3682 from madsmtm/new-version0bbb5cdMerge pull request #3690 from tesuji/android-posix-spawn15c74a4Update version to 0.2.155664947bMerge pull request #3708 from cuviper/ci-sparc64-0.261331dfAlso skipMFD_EXECandMFD_NOEXEC_SEALon sparc6473d2004SkipSECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECVon sparc6480535f3Revert "Upgrade Docker images to Ubuntu 23.10" on sparc64b2b2fd7Readd posix_spawn{_file_actions_t,attr_t} on Android7646277Merge pull request #3686 from redox-os/redox-epoll-0.25eff703redox: correct EPOLL constantsDependabot 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)