HeartSaVioR edited a comment on pull request #33085:
URL: https://github.com/apache/spark/pull/33085#issuecomment-868464382


   Build failed by intention.
   
   https://github.com/HeartSaVioR/spark/runs/2913871777?check_suite_focus=true
   
   It reports scalastyle failure on master branch:
   
   ```
   [error] 
/home/runner/work/spark/spark/sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/state/RocksDBFileManager.scala:28:0:
 
   [error]       Don't import scala.collection.Seq and 
scala.collection.IndexedSeq as it may bring some problems with cross-build 
between Scala 2.12 and 2.13.
   [error] 
   [error]       Please refer below page to see the details of changes around 
Seq / IndexedSeq.
   [error]       
https://docs.scala-lang.org/overviews/core/collections-migration-213.html
   [error] 
   [error]       If you really need to use scala.collection.Seq or 
scala.collection.IndexedSeq, please use the fully-qualified name instead.
   [error]     
   [error] 
/home/runner/work/spark/spark/core/src/main/scala/org/apache/spark/util/Utils.scala:37:0:
 
   [error]       Don't import scala.collection.Seq and 
scala.collection.IndexedSeq as it may bring some problems with cross-build 
between Scala 2.12 and 2.13.
   [error] 
   [error]       Please refer below page to see the details of changes around 
Seq / IndexedSeq.
   [error]       
https://docs.scala-lang.org/overviews/core/collections-migration-213.html
   [error] 
   [error]       If you really need to use scala.collection.Seq or 
scala.collection.IndexedSeq, please use the fully-qualified name instead.
   ```
   
   The fix of above things would happen in different PR, 
https://github.com/apache/spark/pull/33084 


-- 
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.

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