brucearctor opened a new issue, #70013:
URL: https://github.com/apache/doris/issues/70013

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   ### Version
   
   `master` branch (TeamCity build configuration 
`Doris_Coverage_CheckCoverageFe`)
   
   ### What's Wrong?
   
   In TeamCity CI, the `check_coverage_fe (Coverage for Doris FE UT)` pipeline 
(`buildTypeId=Doris_Coverage_CheckCoverageFe`, configured in 
`doris-teamcity-settings`) fails during the container bootstrap step with 
`Process exited with code 4` (`wget` network failure) before running `bash 
build.sh --fe`:
   
   ```text
   [16:29:15]W:  [Step 1/1] + docker run --rm -v 
/home/work/unlimit_teamcity/TeamCity/Agents/20261102142722agent_172.17.0.92_1/system/git/git-01C3C15E.git:/root/git
 -v 
/home/work/unlimit_teamcity/TeamCity/Agents/20261102142722agent_172.17.0.92_1/work/60183217f6ee2a9c:/root/doris
 -w /root/doris apache/doris:build-env-ldb-toolchain-latest bash -c 'cd 
/usr/local/ && wget -t3 -c -q 
https://doris-regression-hk.oss-cn-hongkong-internal.aliyuncs.com/tools/maven/apache-maven-3.9.12-bin.tar.gz
 && tar -zxf apache-maven-3.9.12-bin.tar.gz && export 
PATH=/usr/local/apache-maven-3.9.12/bin:$PATH && mvn --version && cd - && ...'
   [16:29:35]W:  [Step 1/1] Process exited with code 4
   [16:29:35]E:  [Step 1/1] Process exited with code 4 (Step: check_coverage_fe 
(Command Line))
   [16:29:35]E:  [Step 1/1] Step check_coverage_fe (Command Line) failed
   ```
   
   Example failing builds on #69938:
   - 
`http://43.132.222.7:8111/viewLog.html?buildId=1088718&buildTypeId=Doris_Coverage_CheckCoverageFe`
   - 
`http://43.132.222.7:8111/viewLog.html?buildId=1089151&buildTypeId=Doris_Coverage_CheckCoverageFe`
   
   **Root Cause:**
   In the `check_coverage_fe` custom script:
   - Earlier steps on the agent use public OSS endpoints 
(`https://qa-build-hk.oss-cn-hongkong.aliyuncs.com/tools/jacoco-0.8.13.zip` and 
`https://qa-build.oss-cn-beijing.aliyuncs.com/tools/latest/qacli`), which 
succeed.
   - However, `install_maven_cmd` inside `docker run` uses the VPC-internal 
endpoint 
`https://doris-regression-hk.oss-cn-hongkong-internal.aliyuncs.com/tools/maven/apache-maven-3.9.12-bin.tar.gz`:
     ```bash
     install_maven_cmd="cd /usr/local/ && wget -t3 -c -q 
https://doris-regression-hk.oss-cn-hongkong-internal.aliyuncs.com/tools/maven/apache-maven-3.9.12-bin.tar.gz
 && tar -zxf apache-maven-3.9.12-bin.tar.gz && export 
PATH=/usr/local/apache-maven-3.9.12/bin:\$PATH && mvn --version && cd - &&"
     ```
     When the agent/container cannot route to the `cn-hongkong-internal` VPC 
endpoint, `wget -q` fails after 3 attempts (~20s) with exit code `4` (`Network 
failure`).
   
   ### What You Expected?
   
   `Doris_Coverage_CheckCoverageFe` should download 
`apache-maven-3.9.12-bin.tar.gz` from a reachable endpoint (e.g., 
`https://doris-regression-hk.oss-cn-hongkong.aliyuncs.com/tools/maven/apache-maven-3.9.12-bin.tar.gz`
 or falling back to the public endpoint when `-internal` is unreachable) so 
`check_coverage_fe` succeeds consistently.
   
   ### How to Reproduce?
   
   Trigger `run buildall` on a PR targeting `master` that touches FE files 
(e.g. #69938) and inspect the `check_coverage_fe (Coverage for Doris FE UT)` 
TeamCity build log after `P0`, `External`, `NonConcurrent`, and `Cloud_P0` 
complete.
   
   ### Anything Else?
   
   Related to #60918 (where `check_coverage_fe` was previously updated in the 
internal TeamCity configuration) and #67785.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to