This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 5bf1f9152f8f CAMEL-23223: Fix flaky ManagedMessageHistoryAutoConfigIT
5bf1f9152f8f is described below
commit 5bf1f9152f8f0af1b34d0ed18953e5517b67faa5
Author: Guillaume Nodet <[email protected]>
AuthorDate: Tue Jul 7 07:10:57 2026 +0200
CAMEL-23223: Fix flaky ManagedMessageHistoryAutoConfigIT
Increase the OTel metric export interval from 300ms to 5000ms so the
first periodic export fires well after all messages have been processed.
With a short interval, the exporter fires during message processing and
the last exported MetricData may contain incomplete point data, causing
assertions to fail intermittently on slow CI (70% flaky rate).
Closes #24471
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
.../messagehistory/ManagedMessageHistoryAutoConfigIT.java | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
a/components/camel-opentelemetry-metrics/src/test/java/org/apache/camel/opentelemetry/metrics/integration/messagehistory/ManagedMessageHistoryAutoConfigIT.java
b/components/camel-opentelemetry-metrics/src/test/java/org/apache/camel/opentelemetry/metrics/integration/messagehistory/ManagedMessageHistoryAutoConfigIT.java
index 0f4dd7742bf2..66717ddd2b08 100644
---
a/components/camel-opentelemetry-metrics/src/test/java/org/apache/camel/opentelemetry/metrics/integration/messagehistory/ManagedMessageHistoryAutoConfigIT.java
+++
b/components/camel-opentelemetry-metrics/src/test/java/org/apache/camel/opentelemetry/metrics/integration/messagehistory/ManagedMessageHistoryAutoConfigIT.java
@@ -60,7 +60,11 @@ public class ManagedMessageHistoryAutoConfigIT extends
CamelTestSupport {
System.setProperty("otel.traces.exporter", "none");
System.setProperty("otel.logs.exporter", "none");
System.setProperty("otel.propagators", "tracecontext");
- System.setProperty("otel.metric.export.interval", "300");
+ // Use a long export interval so the first periodic export fires well
after all
+ // messages have been processed. With a short interval (e.g. 300ms),
the exporter
+ // fires during message processing and the last exported MetricData
may contain
+ // incomplete point data, causing the assertion to fail intermittently
on slow CI.
+ System.setProperty("otel.metric.export.interval", "5000");
}
@AfterEach
