This is an automated email from the ASF dual-hosted git repository.
davidarthur pushed a change to branch gh-KAFKA-17479-relocate-xml-files
in repository https://gitbox.apache.org/repos/asf/kafka.git
omit 578b7c2e06a turn up logging
omit 1577be3c68c Merge remote-tracking branch 'origin/trunk' into
gh-KAFKA-17479-relocate-xml-files
omit 190df07ace9 KAFKA-17265 Fix flaky
MemoryRecordsBuilderTest#testBuffersDereferencedOnClose (#17092)
omit 0b308b2f48b relocate junit XML files
add e01ee26da8e relocate junit XML files
add 841c5ad1ce7 turn up logging
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 (578b7c2e06a)
\
N -- N -- N refs/heads/gh-KAFKA-17479-relocate-xml-files
(841c5ad1ce7)
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:
.../common/record/MemoryRecordsBuilderTest.java | 42 ++++++++++++++++------
1 file changed, 31 insertions(+), 11 deletions(-)
