Skip to content

[improvement](build) Add build and unit test parallel options to run-fe-ut.sh#63316

Open
heguanhui wants to merge 1 commit into
apache:masterfrom
heguanhui:improvement/fe-ut-parallel
Open

[improvement](build) Add build and unit test parallel options to run-fe-ut.sh#63316
heguanhui wants to merge 1 commit into
apache:masterfrom
heguanhui:improvement/fe-ut-parallel

Conversation

@heguanhui
Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: run-fe-ut.sh does not support build concurrency or unit test execution concurrency. The FE pom.xml already supports the fe_ut_parallel variable (via env.FE_UT_PARALLEL) to control maven-surefire-plugin forkCount, but run-fe-ut.sh never passes this variable, defaulting to 1 JVM for unit tests. This makes FE unit test execution very slow.

Release note

Add -j and -p options to run-fe-ut.sh to support build parallelism and unit test parallelism respectively. -j <num> controls Maven build thread count (passed as -T), and -p <num> controls the number of forked JVMs for running unit tests (passed as FE_UT_PARALLEL env variable which maps to forkCount in maven-surefire-plugin).

Check List (For Author)

  • Test

    • Manual test
  • Behavior changed:

    • No.
  • Does this need documentation?

    • No.

Check List (For Reviewer who merge this PR)

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

…fe-ut.sh

### What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: run-fe-ut.sh does not support build concurrency or unit test execution concurrency. The FE pom.xml already supports the fe_ut_parallel variable (via env.FE_UT_PARALLEL) to control maven-surefire-plugin forkCount, but run-fe-ut.sh never passes this variable, defaulting to 1 JVM for unit tests. This makes FE unit test execution very slow.

### Release note

Add -j and -p options to run-fe-ut.sh to support build parallelism and unit test parallelism respectively.

### Check List (For Author)

- Test: Manual test
- Behavior changed: No
- Does this need documentation: No
@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