[CNM-4667] Fix several flaky TestTracerSuite tests.#46589
Conversation
…retransmitted TCP segments that partially overlapped with previously-counted data.
…reused fd during a later test.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
30 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 6718cd6 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +0.09 | [-2.99, +3.18] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +1.04 | [+0.96, +1.12] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.69 | [+0.48, +0.91] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.12 | [+0.07, +0.17] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | +0.09 | [-2.99, +3.18] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.09 | [+0.05, +0.14] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.07 | [-0.32, +0.46] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.02 | [-0.11, +0.15] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.03, +0.06] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.01 | [-0.40, +0.43] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.49, +0.51] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.12] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.10, +0.08] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.09 | [-0.12, -0.05] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | -0.14 | [-0.30, +0.02] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | -0.20 | [-0.40, +0.01] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.21 | [-0.26, -0.15] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.25 | [-0.31, -0.18] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.26 | [-0.45, -0.08] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | -0.31 | [-0.39, -0.24] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.34 | [-0.57, -0.11] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.56 | [-0.72, -0.41] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -0.84 | [-2.37, +0.69] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_logs | memory utilization | -0.89 | [-1.00, -0.78] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | 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_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | 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_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 |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 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
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, 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, bounds check memory_usage: 10/10 replicas passed. Gate passed.
| if st.hasSentPacket && isSeqBefore(tcp.Seq, st.maxSeqSent) { | ||
| overlap = uint64(st.maxSeqSent - tcp.Seq) | ||
| } | ||
| if uint64(payloadLen) > overlap { |
There was a problem hiding this comment.
should you also check if overlap is bigger than 0?
There was a problem hiding this comment.
I don't think that's needed. overlap defaults to zero and is only set to a positive value when there is overlap (isSeqBefore(tcp.Seq, st.maxSeqSent)). When overlap is 0, which is the common case, the full payloadLen is added to SentBytes.
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
31d06e7
into
main
What does this PR do?
Fixes several flaky eBPFless tests in
TestTracerSuite.TestTracerSuite/eBPFless/TestShortWrite— "couldn't find connection used by short write"updateTCPStats()so it no longer overcountsSentByteswhen the kernel retransmits TCP segments that partially overlap with previously-counted data. We now only add the new bytes beyond the sequence high‑water mark.TestTracerSuite/eBPFless/TestShortWrite— "resource temporarily unavailable"TestShortWritewrite loop to correctly handle the case where the send buffer is completely full and a write returns zero bytes withresource temporarily unavailable.TestTracerSuite/eBPFless/TestTCPRTT— "write: bad file descriptor"TestShortWrite: The original TestShortWrite had a triple-close on the socket fd (defer syscall.Close, explicit unix.Close, and the os.NewFile GC finalizer). After the first close, the kernel could reuse the fd number, so later closes would clobber unrelated fds in other tests. Fixed by consolidating ownership into a single t.Cleanup that does f.Close().Motivation
pkg/network/tracer.TestTracerSuitehas many flaky test failures in CI.Describe how you validated your changes
TestShortWriteconnection‑not‑foundTestShortWriteresource temporarily unavailableTestTCPRTTwrite: bad file descriptor