Skip to content

Conversation

@Mrhs121
Copy link

@Mrhs121 Mrhs121 commented Nov 14, 2025

Purpose of this pull request

Provide a test case for reproduction #10059

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

if (!isEmpty) {
ByteBuffer byteBuffer = null;
while (byteBuffer == null) {
log.info("stopping buffer data...");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to adjust the log level to debug level ?

Copy link
Author

@Mrhs121 Mrhs121 Nov 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to adjust the log level to debug level ?

Thank you for your review. This pr is only used to reproduce the problem and does not need to be merged. This log is written for the convenience of observation, as shown in the GitHub CI logs below, the process is stuck in a loop and continuously print this log.

FYI, this problem can only be reproduced under certain conditions. I also spent quite a lot of time creating this test case. If you are interested, you can try running it locally.
截屏2025-11-15 09 22 44

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok,thx

@davidzollo davidzollo added the don't merge There needs to be a specific reason in the PR, and it cannot be merged for the time being. label Nov 17, 2025
@davidzollo
Copy link
Contributor

good job

Assertions.assertEquals(0, extraCommands.getExitCode(), extraCommands.getStderr());
};

@Disabled
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pr is only used to trigger the ci to reproduce this bug. To speed it up, I manually disabled other irrelevant test cases. You can ignore it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could consider adding a short explanation here, similar to this one:

@Disabled("Performance test, not suitable for regular unit test execution")

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your review ^_^ . This pr is only used to reproduce the problem and does not need to be merged.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have converted it to draft

@zhangshenghang zhangshenghang marked this pull request as draft November 24, 2025 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

connectors-v2 don't merge There needs to be a specific reason in the PR, and it cannot be merged for the time being. doris e2e

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants