Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore](ci) trigger ut if dir gensrc changed #43949

Merged
merged 1 commit into from
Nov 16, 2024
Merged

Conversation

hello-stephen
Copy link
Contributor

@hello-stephen hello-stephen commented Nov 14, 2024

The types in gensrc/build/gen_cpp/Status_types.h and be/src/common/status.h should correspond to each other one by one.

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

The types in gensrc/build/gen_cpp/Status_types.h and be/src/common/status.h should correspond to each other one by one.
@doris-robot
Copy link

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?

@hello-stephen
Copy link
Contributor Author

run buildall

Copy link
Contributor

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Nov 15, 2024
Copy link
Contributor

PR approved by anyone and no changes requested.

@gavinchou gavinchou merged commit 06f5fa8 into master Nov 16, 2024
37 of 39 checks passed
@hello-stephen hello-stephen deleted the hello-stephen-patch-6 branch November 19, 2024 08:11
hello-stephen added a commit to hello-stephen/doris that referenced this pull request Nov 19, 2024
hello-stephen added a commit that referenced this pull request Nov 19, 2024
### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #43949
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by one committer. dev/3.0.3-merged reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants