-
Notifications
You must be signed in to change notification settings - Fork 1.3k
8000 [serverless-init] Fix flushing error logs #37710
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
[serverless-init] Fix flushing error logs #37710
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 5e0edb6 Optimization Goals: ✅ Improvement(s) detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_memory | memory utilization | +2.98 | [+2.84, +3.13] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.46 | [-2.31, +3.23] | 1 | Logs bounds checks dashboard |
➖ | ddot_logs | memory utilization | +0.39 | [+0.27, +0.51] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.14 | [+0.08, +0.20] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.03 | [-0.58, +0.65] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.03 | [-0.49, +0.55] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.56, +0.58] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.01 | [-0.23, +0.25] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.27, +0.28] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.03, +0.02] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.03 | [-0.62, +0.55] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.04 | [-0.63, +0.56] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.05 | [-0.70, +0.60] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.14 | [-0.74, +0.46] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.15 | [-0.22, -0.08] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.27 | [-0.31, -0.22] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.34 | [-0.50, -0.18] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.47 | [-0.59, -0.35] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.62 | [-0.75, -0.49] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.63 | [-1.49, +0.24] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -1.07 | [-1.22, -0.92] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_cpu | % cpu utilization | -1.23 | [-4.30, +1.84] | 1 | Logs |
✅ | file_tree | memory utilization | -6.15 | [-6.35, -5.95] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_logs | memory_usage | 5/10 | bounds checks dashboard |
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
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".
CI Pass/Fail Decision
❌ Failed. Some Quality Gates were violated.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 5/10 replicas passed. Failed 5 which is > 0. Gate FAILED.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
@@ -37,7 +37,7 @@ func (cw *ChannelWriter) Write(p []byte) (n int, err error) { | |||
// Flush full stacktrace without splitting by new line | |||
if cw.IsError { | |||
cw.sendPayload(p) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we confirm that whoever reads the data from the cw.Channel
that ultimately gets the payload isn't going to run into any kind of bytes corruption issues? (or we can clone the buffer before wending it along)
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Fixes the
ChannelWriter.Write
method to return the full byte count after flushingstderr
, preventing the writer from retrying the same payload indefinitely.Motivation
Bug introduced in #37551
Describe how you validated your changes
Tested manually
Possible Drawbacks / Trade-offs