Prepare a clean Doris package and run Docker regression tests, which check whether changes break existing behavior. Restore configuration and startup files from Git, build the test image, and investigate failures using configuration checks and runtime logs.
Run Doris docker-based regression tests from a clean package
Review the instructions the agent will receive before you install.
Run Doris docker-based regression tests from a clean package, avoiding contamination from local conf/ or startup script modifications.
Requires Python 3. Install dependencies from docker/runtime/doris-compose/requirements.txt:
python -m pip install --user -r docker/runtime/doris-compose/requirements.txt
If installation fails (especially PyYAML conflicts), use specific versions:
python -m pip install --user pyyaml==5.3.1 docker==6.1.3
python -m pip install --user -r docker/runtime/doris-compose/requirements.txt
Alternatively, use a virtual environment:
python -m venv doris-compose-env
source doris-compose-env/bin/activate
pip install -r docker/runtime/doris-compose/requirements.txt
docker run hello-world # Docker works
docker compose version # Compose v2
docker-compose version # Should resolve to Compose v2
If docker-compose shows TypeError: kwargs_from_env(), make sure it is indeed Docker Compose V2; if not, you need to install and point to the correct version.
Check port availability:
lsof -nP -iTCP:8030,8040,8050,8060,8070,9010,9020,9030,9050,9060 -sTCP:LISTEN
If there is a conflict, ask the user how to handle it.
./build.sh --fe --be -j<parallel_jobs> --output <output_directory>
Sanitize configs from git HEAD:
git show HEAD:conf/fe.conf > <output_directory>/fe/conf/fe.conf
git show HEAD:conf/be.conf > <output_directory>/be/conf/be.conf
git show HEAD:bin/start_fe.sh > <output_directory>/fe/bin/start_fe.sh
chmod 755 <output_directory>/fe/bin/start_fe.sh
Verify clean configs use default ports:
fe.conf: 8030, 9020, 9030, 9010, 8070be.conf: 9060, 8040, 9050, 8060, 8050start_fe.sh: no -agentlib:jdwp debug agentdocker build \
--build-arg OUTPUT_PATH=<output_directory> \
-f docker/runtime/doris-compose/Dockerfile \
-t <image_name>:latest \
.
Create regression-test/conf/regression-conf-custom.groovy:
image = "<image_name>:latest"
excludeDockerTest = false
testGroups = "docker"
./run-regression-test.sh --run -d <directory> -s <suite_name>
| Symptom | Cause | Fix |
|---|---|---|
| 0 suites | excludeDockerTest=true or missing testGroups="docker" | Check regression-conf-custom.groovy |
| JDWP error | start_fe.sh has debug agent | Re-sanitize from git show HEAD:bin/start_fe.sh |
| Wrong ports | Configs have local edits | Re-sanitize from git show HEAD:conf/fe.conf / be.conf |
| Port conflict | Processes using default ports | lsof then kill |
Runtime cluster at /tmp/doris/<suite_name>/:
fe-1/log/fe.log, fe.warn.log, fe.out, health.outbe-1/log/be.INFO, be.WARNING, be.out, health.outdoris-compose.log# 1. Check environment
python --version
docker run hello-world
docker compose version
lsof -nP -iTCP:8030,8040,8050,8060,8070,9010,9020,9030,9050,9060 -sTCP:LISTEN
# 2. Build
./build.sh --fe --be -j60
# 3. Sanitize package configs
git show HEAD:conf/fe.conf > <output_directory>/fe/conf/fe.conf
git show HEAD:conf/be.conf > <output_directory>/be/conf/be.conf
git show HEAD:bin/start_fe.sh > <output_directory>/fe/bin/start_fe.sh
chmod 755 <output_directory>/fe/bin/start_fe.sh
# 4. Build image
docker build --build-arg OUTPUT_PATH=<output_directory> -f docker/runtime/doris-compose/Dockerfile -t <image_name>:latest .
# 5. Configure (create regression-conf-custom.groovy)
# 6. Run
./run-regression-test.sh --run -d <directory> -s <suite_name>
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Format C++ code in the BE and Cloud modules using the project's clang-format v16 rules. Use the provided scripts to fix formatting or check for violations without changing files, then review the resulting differences before committing.
Run clang-tidy static analysis, which checks code without executing it, on added or modified BE and Cloud C++ files. Focus diagnostics on changed lines, investigate bug, performance, and readability warnings, and verify fixes with another check.
Review Doris code changes using project-specific checklists for data correctness, concurrency, memory safety, compatibility, performance, and tests. Trace related code paths and explain findings with concrete failure scenarios, using query plan trees when reviewing optimizer behavior.
Diagnoses and fixes Java style violations in the FE module using Checkstyle, a tool that checks coding rules. It interprets errors, applies the project's formatting and import restrictions, and reruns checks to verify fixes.