-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-45665][INFRA] Uses different ORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branches
#43496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branchesORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branches
| "SCALA_PROFILE": "scala2.13", | ||
| "PYTHON_TO_TEST": "" | ||
| "PYTHON_TO_TEST": "", | ||
| "ORACLE_DOCKER_IMAGE_NAME": "gvenzl/oracle-xe:21.3.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build_and_test.yml in branch-3.3 is configured as oracle-xe:18.4.0, but the previous daily test has always used oracle-xe:21.3.0, so it is still configured as oracle-xe:21.3.0 here.
ORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branchesORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branches
|
I've tested this solution in my personal repository, and it should be feasible. branch-3.3: https://github.com/LuciferYang/spark/actions/runs/6643102365/job/18054383056
branch-3.4: https://github.com/LuciferYang/spark/actions/runs/6637023118
branch-3.5: https://github.com/LuciferYang/spark/actions/runs/6637015146/job/18065960793
|
ORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branchesORACLE_DOCKER_IMAGE_NAME in the scheduled builds in other branches
|
Merged into master. I will keep an eye on tomorrow's daily test. |
|
Thanks @HyukjinKwon ~ |
|
+1, late LGTM. |
|
Thanks @dongjoon-hyun ~ |
|
branch-3.3:https://github.com/apache/spark/actions/runs/6650581612 All passed ~ |



What changes were proposed in this pull request?
#43123 upgraded the version of Oracle used for testing. As the daily test will reuse
build_and_test.yml, the branch-3.x will also use the new version. However, due to the lack of synchronized code changes, theOracleIntegrationSuitein theDocker integration testscannot pass the test during the daily test of branch-3.x:So this PR adds the ORACLE_DOCKER_IMAGE_NAME environment variable to the daily test yml file for branch-3.x and uses the previous version of the Oracle Docker image that can pass the test successfully.
Why are the changes needed?
Restore the daily test for branch-3.x.
Does this PR introduce any user-facing change?
No,dev-only
How was this patch tested?
Monitor the daily test results.
Was this patch authored or co-authored using generative AI tooling?
No