[ https://issues.apache.org/jira/browse/SPARK-45651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780127#comment-17780127 ]
Hyukjin Kwon edited comment on SPARK-45651 at 10/27/23 12:48 AM: ----------------------------------------------------------------- Reverted in https://github.com/apache/spark/commit/df0262f29969fe40f53dee070a150f2bfe98484c and https://github.com/apache/spark/commit/0d665fe8c87b037516f21162d2f5545580776af3 was (Author: gurwls223): Reverted in https://github.com/apache/spark/commit/df0262f29969fe40f53dee070a150f2bfe98484c > Snapshots of some packages are not published any more > ----------------------------------------------------- > > Key: SPARK-45651 > URL: https://issues.apache.org/jira/browse/SPARK-45651 > Project: Spark > Issue Type: Bug > Components: Build > Affects Versions: 4.0.0 > Reporter: Enrico Minack > Priority: Major > Labels: pull-request-available > > Snapshots of some packages are not been published anymore, e.g. > spark-sql_2.13-4.0.0 has not been published since Sep, 13th: > https://repository.apache.org/content/groups/snapshots/org/apache/spark/spark-sql_2.13/4.0.0-SNAPSHOT/ > There have been some attempts to fix CI: SPARK-45535 SPARK-45536 > Assumption is that memory consumption during build exceeds the available > memory of the Github host. > The following could be attempted: > - enable manual trigger of the {{publish_snapshots.yml}} workflow > - enable some memory use logging to proof that exceeded memory is the root > cause > - attempt to reduce memory footprint and see impact in above logging > - revert memory use logging -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org