Skip to content
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

Opcode Suite fails for Scala 2.13.8+ #11174

Open
razajafri opened this issue Jul 12, 2024 · 1 comment
Open

Opcode Suite fails for Scala 2.13.8+ #11174

razajafri opened this issue Jul 12, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@razajafri
Copy link
Collaborator

The Opcode tests in OpcodeSuite.scala fail when using scala.version 2.13.8+ with the following exception

- IFNONNULL opcode *** FAILED ***
  [,z,] did not equal [,z,z] (OpcodeSuite.scala:62)

We need to add support for it in the udf-compiler.

@razajafri razajafri added bug Something isn't working ? - Needs Triage Need team to review and classify labels Jul 12, 2024
razajafri added a commit to razajafri/spark-rapids that referenced this issue Jul 12, 2024
There is a bytecode incompatibility which is why we are skipping these
until we add support for it. For details please see the following two
issues
NVIDIA#11174
NVIDIA#10203
razajafri added a commit that referenced this issue Jul 16, 2024
…s] (#10994)

* POM changes for Spark 4.0.0

Signed-off-by: Raza Jafri <rjafri@nvidia.com>

* validate buildver and scala versions

* more pom changes

* fixed the scala-2.12 comment

* more fixes for scala-2.13 pom

* addressed comments

* add in shim check to account for 400

* add 400 for premerge tests against jdk 17

* temporarily remove 400 from snapshotScala213

* fixed 2.13 pom

* Remove 400 from jdk17 as it will compile with Scala 2.12

* github workflow changes

* added quotes to pom-directory

* update version defs to include scala 213 jdk 17

* Cross-compile all shims from JDK17 to JDK8

Eliminate Logging inheritance to prevent shimming of unshimmable API
classes

Signed-off-by: Gera Shegalov <gera@apache.org>

* dummy

* undo api pom change

Signed-off-by: Gera Shegalov <gera@apache.org>

* Add preview1 to the allowed shim versions

Signed-off-by: Gera Shegalov <gera@apache.org>

* Scala 2.13 to require JDK17

Signed-off-by: Gera Shegalov <gera@apache.org>

* Removed unused import left over from razajafri#3

* Setup JAVA_HOME before caching

* Only upgrade the Scala plugin for Scala 2.13

* Regenerate Scala 2.13 poms

* Remove 330 from JDK17 builds for Scala 2.12

* Revert "Remove 330 from JDK17 builds for Scala 2.12"

This reverts commit 1faabd4.

* Downgrade scala.plugin.version for cloudera

* Updated comment to include the issue

* Upgrading the scala.maven.plugin version to 4.9.1 which is the same as Spark 4.0.0

* Downgrade scala-maven-plugin for Cloudera

* revert mvn verify changes

* Avoid cache for JDK 17

* removed cache dep from scala 213
* Added Scala 2.13 specific checks

* Handle the change for UnaryPositive now extending RuntimeReplaceable

* Removing 330 from jdk17.buildvers as we only support Scala2.13 and fixing the enviornment variable in version-defs.sh that we read for building against JDK17 with Scala 213

* Update Scala 2.13 poms

* fixed scala2.13 verify to actually use the scala2.13/pom.xml

* Added missing csv files

* Skip Opcode tests

There is a bytecode incompatibility which is why we are skipping these
until we add support for it. For details please see the following two
issues
#11174
#10203

* upmerged and fixed the new compile error introduced

* addressed review comments

* Removed jdk17 cloudera check and moved it inside the 321,330 and 332 cloudera profiles

* fixed upmerge conflicts

* reverted renaming of id

* Fixed HiveGenericUDFShim

* addressed review comments

* reverted the debugging code

* generated Scala 2.13 poms

---------

Signed-off-by: Raza Jafri <rjafri@nvidia.com>
Signed-off-by: Gera Shegalov <gera@apache.org>
Co-authored-by: Gera Shegalov <gera@apache.org>
@mattahrens mattahrens removed the ? - Needs Triage Need team to review and classify label Jul 16, 2024
@mattahrens mattahrens assigned razajafri and abellina and unassigned razajafri Jul 16, 2024
@mattahrens
Copy link
Collaborator

@abellina can you triage this issue to understand the potential fix needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants