This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch feature/CAMEL-23712-traceCustomIdOnly
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 23b7fd634781 CAMEL-23712: Fix camel-telemetry-dev tests for reduced
endpoint-sending spans
discard 1facf2c5e562 CAMEL-23712: Add traceCustomIdOnly option to only trace
processors with custom IDs
add ed9eb9674b5a CAMEL-23709: Update micrometer-observability tests for
EndpointSending span reduction
add 5c2403740cfb CAMEL-23712: Add traceCustomIdOnly option to only trace
processors with custom IDs
add 7adddf09deab CAMEL-23712: Fix camel-telemetry-dev tests for reduced
endpoint-sending spans
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (23b7fd634781)
\
N -- N -- N refs/heads/feature/CAMEL-23712-traceCustomIdOnly
(7adddf09deab)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../camel/micrometer/observability/BaggageInjectionTest.java | 7 ++-----
.../apache/camel/micrometer/observability/BaggageSettingTest.java | 5 ++---
.../camel/micrometer/observability/EnableProcessorsTest.java | 7 ++-----
.../org/apache/camel/micrometer/observability/SpanBeanTest.java | 7 ++-----
.../camel/micrometer/observability/SpanCustomizationTest.java | 7 ++-----
.../apache/camel/micrometer/observability/SpanInjectionTest.java | 7 ++-----
6 files changed, 12 insertions(+), 28 deletions(-)
