Fix PythonApiTests Jenkins failure by using portable worker path configuration#713
Fix PythonApiTests Jenkins failure by using portable worker path configuration#713mohit-devlogs wants to merge 1 commit intoapache:mainfrom
Conversation
|
Thank you @mohit-devlogs. I think we had tried with the "../../" relative path solutions but it was still breaking. @mspruc can you confirm that? |
Thanks for the clarification. I have used the relative path method for this PR. It means that the worker path will not be an absolute path from the CI environment; it will be a relative path from the project structure. It should also be noted if this method is different from what you were trying to implement earlier. I am also willing to change this if there are any known issues with this method. This method has already been tested, and the PythonApiTests are running successfully on Jenkins using this method. Earlier, they were not running using this method. |
|
@zkaoudi I'm not sure i tried with @mohit-devlogs What steps have you taken to verify the worker works now that you've changed the test? |
|
To verify this, the Python API test is run locally using the following command: The build was completed successfully, and the test was able to locate the worker based on the relative path setup. The purpose of this modification is to avoid the use of paths in the environment. Instead, it is based on the relative paths. |
Fixes #642
The PythonApiTests test class was using a machine-specific absolute path for the Python worker script in the wayang.properties file, which was causing the Jenkins builds to fail in CI environments.
This PR changes the absolute path to a relative path, which is correct and portable, so that it can correctly resolve the path within the repository structure. The test class PythonApiTests was also using an unnecessary worker path override, which is removed in this PR so that it uses the test configuration provided in src/test/resources.