Skip to content

[test](schema-change) log alter job state in test_schema_change_mow_with_empty_rowset#64903

Open
shuke987 wants to merge 1 commit into
apache:masterfrom
shuke987:fix/log-jobstate-empty-rowset
Open

[test](schema-change) log alter job state in test_schema_change_mow_with_empty_rowset#64903
shuke987 wants to merge 1 commit into
apache:masterfrom
shuke987:fix/log-jobstate-empty-rowset

Conversation

@shuke987

Copy link
Copy Markdown
Collaborator

Proposed changes

Add a logger.info to print the alter table job state that is polled inside the Awaitility loop in test_schema_change_mow_with_empty_rowset.groovy.

The test waits for the schema-change job to reach FINISHED/CANCELLED but does not log the intermediate state. When the job stalls or ends up CANCELLED, the regression log shows no trace of the observed state, making failures hard to diagnose. Logging the polled res each iteration makes such failures self-explanatory from the test output.

No behavior change to the test logic itself.

Checklist

  • No new test needed (logging-only change to an existing regression test)
    🤖 Generated with Claude Code

…ith_empty_rowset

Add a logger.info for the alter table job state polled inside the
Awaitility loop so failures are easier to diagnose from regression logs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants