Skip to content

Conversation

@HyukjinKwon
Copy link
Member

What changes were proposed in this pull request?

This PR is a followup of #35594 that recovers Mima compatibility test for Scala 2.13.

Why are the changes needed?

To fix the Mima build broken (https://github.com/apache/spark/actions/runs/3380379538/jobs/5613108397)

[error] spark-core: Failed binary compatibility check against org.apache.spark:spark-core_2.13:3.3.0! Found 2 potential problems (filtered 945)
[error]  * method productElementName(Int)java.lang.String in object org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown.productElementName")
[error]  * method productElementNames()scala.collection.Iterator in object org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown.productElementNames")

Does this PR introduce any user-facing change?

No, dev-only.

How was this patch tested?

CI in this PR should test it out. After that, scheduled jobs for Scala 2.13 will test this out

@HyukjinKwon
Copy link
Member Author

cc @cloud-fan and @AngersZhuuuu FYI

@github-actions github-actions bot added the BUILD label Nov 3, 2022
@AngersZhuuuu
Copy link
Contributor

Why origin PR #35594 GA passed, what changed?

@HyukjinKwon
Copy link
Member Author

We don't run Scala 2.13 build in PR builder, but only in scheduled jobs https://github.com/apache/spark/actions

@AngersZhuuuu
Copy link
Contributor

We don't run Scala 2.13 build in PR builder, but only in scheduled jobs https://github.com/apache/spark/actions

Got it, thanks.

@HyukjinKwon
Copy link
Member Author

Merged to master.

SandishKumarHN pushed a commit to SandishKumarHN/spark that referenced this pull request Dec 12, 2022
…tElementNames in Mima for Scala 2.13

### What changes were proposed in this pull request?
This PR is a followup of apache#35594 that recovers Mima compatibility test for Scala 2.13.

### Why are the changes needed?

To fix the Mima build broken (https://github.com/apache/spark/actions/runs/3380379538/jobs/5613108397)

```
[error] spark-core: Failed binary compatibility check against org.apache.spark:spark-core_2.13:3.3.0! Found 2 potential problems (filtered 945)
[error]  * method productElementName(Int)java.lang.String in object org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown.productElementName")
[error]  * method productElementNames()scala.collection.Iterator in object org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages#Shutdown.productElementNames")
```

### Does this PR introduce _any_ user-facing change?
No, dev-only.

### How was this patch tested?
CI in this PR should test it out. After that, scheduled jobs for Scala 2.13 will test this out

Closes apache#38492 from HyukjinKwon/SPARK-38270-followup.

Authored-by: Hyukjin Kwon <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
@HyukjinKwon HyukjinKwon deleted the SPARK-38270-followup branch January 15, 2024 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants