chi3316 opened a new issue, #8510: URL: https://github.com/apache/rocketmq/issues/8510
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Github Action ### RocketMQ version 5.2.0 ### JDK Version _No response_ ### Describe the Bug The CI pipeline for the Go e2e tests in the RocketMQ GitHub repository is failing due to an issue with the run.sh script. Specifically, the script attempts to source the env.sh file using source but encounters an error indicating that the file cannot be found. As a result, the script fails to execute properly, leading to the CI pipeline failure with an exit code of 2. ### Steps to Reproduce 1. Trigger the CI pipeline in the GitHub Actions workflow. 2. Observe the failure in the Test E2E golang test stage. 3. Checking the logs, you can see that the exit code for the container is 2  ### What Did You Expect to See? Test E2E golang where the container exit status code is 0 and the pipeline passes normally ### What Did You See Instead? The Test E2E golang cannot be executed, causing the CI pipeline to fail. ### Additional Context _No response_ -- 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]
