-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[DO NOT MERGE] CI test #12264
[DO NOT MERGE] CI test #12264
Conversation
I made 3 attempts in my PR. Attempt 1test-spark-java17-java-tests (scala-2.12, spark3.4, hudi-spark-datasource/hudi-spark3.4.x)
test-spark-java17-java-tests (scala-2.12, spark3.4, hudi-spark-datasource/hudi-spark3.4.x)
docker-java17-test (scala-2.12, flink1.20, spark3.4, spark3.4.0)
Attempt 2test-spark-java17-java-tests (scala-2.12, spark3.4, hudi-spark-datasource/hudi-spark3.4.x)
docker-java17-test (scala-2.12, flink1.20, spark3.4, spark3.4.0)
Attempt 3integration-tests (spark3.5, spark-3.5.3/spark-3.5.3-bin-hadoop3.tgz)
test-spark-java-tests (scala-2.12, spark3.4, hudi-spark-datasource/hudi-spark3.4.x)
test-spark-scala-tests (scala-2.12, spark3.4, hudi-spark-datasource/hudi-spark3.4.x)
|
@codope , if you don't mind, could you, please, take a look at functional Scala test |
Yeah I noticed it's flaky. I'll take a look. |
a4bda8f
to
412334a
Compare
412334a
to
145ac96
Compare
Change Logs
I've started to face problems with Github Actions CI after force push in my PR: #12245, and force push changes were related to changing new test and rebase on current master. Decided to check current state in this CI test MR.
Impact
No
Risk level (write none, low medium or high below)
No
Documentation Update
No
Contributor's checklist