QCLyu commented on PR #11495:
URL: 
https://github.com/apache/incubator-gluten/pull/11495#issuecomment-3903201773

   > Hi @PHILO-HE , are you aware of any recent migration from java to scala 
regarding TreeMemoryConsumers? The challenge is I couldn't test compliers 
locally after making changes, and pushing blind commits is very inefficient. It 
always failed with sth similar to the following error: `[ERROR] Failed to 
execute goal net.alchim31.maven:scala-maven-plugin:4.9.2:compile 
(scala-compile-first) on project gluten-core: Execution scala-compile-first of 
goal net.alchim31.maven:scala-maven-plugin:4.9.2:compile failed: Failed to find 
name hashes for org.apache.gluten.memory.memtarget.spark.TreeMemoryConsumers`
   > 
   > By switching to the main branch, the same error persisted. My guess is a 
migration from Scala to Java happened recently. Checked that 
TreeMemoryConsumers exists only as a .java file in the main branch (cc 
@zhztheplayer ).
   > 
   > What I have tried:
   > 
   > * Standard Clean Build (mvn clean package)
   > * Bypass Zinc Server (-Dscala.useZincServer=false)
   > * Manual File Search (Checking for ghost .scala files)
   > * Nuke and Pave (Manual rm -rf target/)
   > * Forces the Scala compiler to look at Java source files in the same pass 
(added configuration in pom.xml)
   > 
   > So far all the above methods failed. How I generally test locally before 
pushing PR: mvn clean package -Pbackends-velox -Pspark-3.5 -DskipTests Or, 
simply mvn clean package -DskipTests These local tests were generally useful 
before I took a break.
   > 
   > Would appreciate guidance or contexts.
   
   Created a separate issue #11616 . Please correct me if I'm wrong (or 
overthinking).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to